From: osstest service user <osstest@xenbits.xen.org>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com, keir@xen.org,
stefano.stabellini@eu.citrix.com
Subject: [ovmf bisection] complete build-i386-xsm
Date: Sat, 13 Jun 2015 03:58:25 +0000 [thread overview]
Message-ID: <E1Z3caP-0001xd-93@osstest.test-lab.xenproject.org> (raw)
branch xen-unstable
xen branch xen-unstable
job build-i386-xsm
test xen-build
Tree: ovmf https://github.com/tianocore/edk2.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: ovmf https://github.com/tianocore/edk2.git
Bug introduced: fe32096778cf248e36d6d00cd958d73fb903126f
Bug not present: e63ec1beac46991176b18c859372f0f16fb97b13
commit fe32096778cf248e36d6d00cd958d73fb903126f
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date: Thu Jun 11 07:14:18 2015 +0000
PcAtChipsetPkg/PcRtc: Fix a Y2K bug
The original driver cannot handle the case when system time runs from 1999/12/31 23:59:59
to 2000/1/1 0:0:0.
A simple test to set system time to 1999/12/31 23:59:59 can expose this bug.
The patch limits the driver to only support year in 100 range and decide the century value based
on the supporting range: Century either equals to PcdMinimalYear / 100 or equals to PcdMinimalYear / 100 + 1.
The patch passed the Y2K test.
However with year range [1998, 2097], when system time is 2097/12/31 23:59:59,
the next second system time will become 1998/1/1 0:0:0. I think it's a acceptable limitation.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
Reviewed-by: Feng Tian <feng.tian@intel.com>
git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@17624 6f19259b-4bc3-4df7-8a09-765794883524
For bisection revision-tuple graph see:
http://logs.test-lab.xenproject.org/osstest/results/bisect.ovmf.build-i386-xsm.xen-build.html
Revision IDs in each graph node refer, respectively, to the Trees above.
----------------------------------------
Searching for failure / basis pass:
58425 fail [host=nocera0] / 58398 [host=nocera1] 58344 [host=nocera1] 58299 [host=nocera1] 58249 ok.
Failure / basis pass flights: 58425 / 58249
(tree with no url: seabios)
(tree in basispass but not in latest: qemu)
Tree: ovmf https://github.com/tianocore/edk2.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
Tree: xen git://xenbits.xen.org/xen.git
Latest 0614d73be31da5ca1e420ea268a9f13f6aca659d e15907a474fe03ca13fca067b7046b77122484cb 12e817e281034f5881f46e0e4f1d127820101a78
Basis pass d863e127a25b2195ca0e01f2c92f139a573e15e9 b2da824bc5ad35fb9f1e74a203d7be96a7b0345e ecdae1cfaa7f6123decaa1b9d7205c3ff726b941
Generating revisions with ./adhoc-revtuple-generator https://github.com/tianocore/edk2.git#d863e127a25b2195ca0e01f2c92f139a573e15e9-0614d73be31da5ca1e420ea268a9f13f6aca659d git://xenbits.xen.org/staging/qemu-upstream-unstable.git#b2da824bc5ad35fb9f1e74a203d7be96a7b0345e-e15907a474fe03ca13fca067b7046b77122484cb git://xenbits.xen.org/xen.git#ecdae1cfaa7f6123decaa1b9d7205c3ff726b941-12e817e281034f5881f46e0e4f1d127820101a78
+ exec
+ sh -xe
+ cd /home/osstest/repos/edk2
+ git remote set-url origin git://cache:9419/https://github.com/tianocore/edk2.git
+ git fetch -p origin +refs/heads/*:refs/remotes/origin/*
+ exec
+ sh -xe
+ cd /home/osstest/repos/qemu-upstream-unstable
+ git remote set-url origin git://cache:9419/git://xenbits.xen.org/staging/qemu-upstream-unstable.git
+ git fetch -p origin +refs/heads/*:refs/remotes/origin/*
+ exec
+ sh -xe
+ cd /home/osstest/repos/xen
+ git remote set-url origin git://cache:9419/git://xenbits.xen.org/xen.git
+ git fetch -p origin +refs/heads/*:refs/remotes/origin/*
+ exec
+ sh -xe
+ cd /home/osstest/repos/edk2
+ git remote set-url origin git://cache:9419/https://github.com/tianocore/edk2.git
+ git fetch -p origin +refs/heads/*:refs/remotes/origin/*
+ exec
+ sh -xe
+ cd /home/osstest/repos/qemu-upstream-unstable
+ git remote set-url origin git://cache:9419/git://xenbits.xen.org/staging/qemu-upstream-unstable.git
+ git fetch -p origin +refs/heads/*:refs/remotes/origin/*
+ exec
+ sh -xe
+ cd /home/osstest/repos/xen
+ git remote set-url origin git://cache:9419/git://xenbits.xen.org/xen.git
+ git fetch -p origin +refs/heads/*:refs/remotes/origin/*
Loaded 3005 nodes in revision graph
Searching for test results:
58249 pass d863e127a25b2195ca0e01f2c92f139a573e15e9 b2da824bc5ad35fb9f1e74a203d7be96a7b0345e ecdae1cfaa7f6123decaa1b9d7205c3ff726b941
58344 [host=nocera1]
58299 [host=nocera1]
58438 fail 0614d73be31da5ca1e420ea268a9f13f6aca659d e15907a474fe03ca13fca067b7046b77122484cb 12e817e281034f5881f46e0e4f1d127820101a78
58455 pass e63ec1beac46991176b18c859372f0f16fb97b13 e15907a474fe03ca13fca067b7046b77122484cb 12e817e281034f5881f46e0e4f1d127820101a78
58425 fail 0614d73be31da5ca1e420ea268a9f13f6aca659d e15907a474fe03ca13fca067b7046b77122484cb 12e817e281034f5881f46e0e4f1d127820101a78
58432 pass d863e127a25b2195ca0e01f2c92f139a573e15e9 b2da824bc5ad35fb9f1e74a203d7be96a7b0345e ecdae1cfaa7f6123decaa1b9d7205c3ff726b941
58443 pass 071586ee476b0c1325a008c6535dd4d2064252ab e15907a474fe03ca13fca067b7046b77122484cb 7c9a93a013783a3344032445469d6b87e496aca4
58446 pass e63ec1beac46991176b18c859372f0f16fb97b13 e15907a474fe03ca13fca067b7046b77122484cb 12e817e281034f5881f46e0e4f1d127820101a78
58453 pass e63ec1beac46991176b18c859372f0f16fb97b13 e15907a474fe03ca13fca067b7046b77122484cb 12e817e281034f5881f46e0e4f1d127820101a78
58444 pass 13af4ab06516eefb40fb985467141e09efe9c58b e15907a474fe03ca13fca067b7046b77122484cb 860313f0411d2dcc6b2fd78bfb834b39d05373a6
58445 pass 2a697cb579972d1b849c396499dd0a1d2e911d35 e15907a474fe03ca13fca067b7046b77122484cb 12e817e281034f5881f46e0e4f1d127820101a78
58448 fail fe9dfae5149af20c08127fb5849dbb0ae44c71ae e15907a474fe03ca13fca067b7046b77122484cb 12e817e281034f5881f46e0e4f1d127820101a78
58452 fail fe32096778cf248e36d6d00cd958d73fb903126f e15907a474fe03ca13fca067b7046b77122484cb 12e817e281034f5881f46e0e4f1d127820101a78
58454 fail fe32096778cf248e36d6d00cd958d73fb903126f e15907a474fe03ca13fca067b7046b77122484cb 12e817e281034f5881f46e0e4f1d127820101a78
58456 fail fe32096778cf248e36d6d00cd958d73fb903126f e15907a474fe03ca13fca067b7046b77122484cb 12e817e281034f5881f46e0e4f1d127820101a78
58398 [host=nocera1]
Searching for interesting versions
Result found: flight 58249 (pass), for basis pass
Result found: flight 58425 (fail), for basis failure
Repro found: flight 58432 (pass), for basis pass
Repro found: flight 58438 (fail), for basis failure
0 revisions at e63ec1beac46991176b18c859372f0f16fb97b13 e15907a474fe03ca13fca067b7046b77122484cb 12e817e281034f5881f46e0e4f1d127820101a78
No revisions left to test, checking graph state.
Result found: flight 58446 (pass), for last pass
Result found: flight 58452 (fail), for first failure
Repro found: flight 58453 (pass), for last pass
Repro found: flight 58454 (fail), for first failure
Repro found: flight 58455 (pass), for last pass
Repro found: flight 58456 (fail), for first failure
*** Found and reproduced problem changeset ***
Bug is in tree: ovmf https://github.com/tianocore/edk2.git
Bug introduced: fe32096778cf248e36d6d00cd958d73fb903126f
Bug not present: e63ec1beac46991176b18c859372f0f16fb97b13
+ exec
+ sh -xe
+ cd /home/osstest/repos/edk2
+ git remote set-url origin git://cache:9419/https://github.com/tianocore/edk2.git
+ git fetch -p origin +refs/heads/*:refs/remotes/origin/*
commit fe32096778cf248e36d6d00cd958d73fb903126f
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date: Thu Jun 11 07:14:18 2015 +0000
PcAtChipsetPkg/PcRtc: Fix a Y2K bug
The original driver cannot handle the case when system time runs from 1999/12/31 23:59:59
to 2000/1/1 0:0:0.
A simple test to set system time to 1999/12/31 23:59:59 can expose this bug.
The patch limits the driver to only support year in 100 range and decide the century value based
on the supporting range: Century either equals to PcdMinimalYear / 100 or equals to PcdMinimalYear / 100 + 1.
The patch passed the Y2K test.
However with year range [1998, 2097], when system time is 2097/12/31 23:59:59,
the next second system time will become 1998/1/1 0:0:0. I think it's a acceptable limitation.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
Reviewed-by: Feng Tian <feng.tian@intel.com>
git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@17624 6f19259b-4bc3-4df7-8a09-765794883524
Revision graph left in /home/logs/results/bisect.ovmf.build-i386-xsm.xen-build.{dot,ps,png,html}.
----------------------------------------
58456: tolerable ALL FAIL
flight 58456 ovmf real-bisect [real]
http://logs.test-lab.xenproject.org/osstest/logs/58456/
Failures :-/ but no regressions.
Tests which did not succeed,
including tests which could not be run:
build-i386-xsm 5 xen-build fail baseline untested
jobs:
build-i386-xsm fail
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
next reply other threads:[~2015-06-13 3:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 3:58 osstest service user [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-05 3:35 [ovmf bisection] complete build-i386-xsm osstest service owner
2022-03-03 19:58 osstest service owner
2021-12-09 17:09 osstest service owner
2021-09-02 7:36 osstest service owner
2019-01-09 10:13 osstest service owner
2018-11-09 2:13 osstest service owner
2018-07-19 9:10 osstest service owner
2017-09-22 7:37 osstest service owner
2017-09-11 23:47 osstest service owner
2017-07-06 12:49 osstest service owner
2016-06-29 21:38 osstest service owner
2015-12-08 18:03 osstest service owner
2015-05-21 0:11 osstest service user
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Z3caP-0001xd-93@osstest.test-lab.xenproject.org \
--to=osstest@xenbits.xen.org \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).