From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [xen-unstable-smoke bisection] complete build-arm64-xsm
Date: Wed, 14 Mar 2018 02:29:21 +0000 [thread overview]
Message-ID: <E1evwAL-0001ri-7m@osstest.test-lab.xenproject.org> (raw)
branch xen-unstable-smoke
xenbranch xen-unstable-smoke
job build-arm64-xsm
testid xen-build
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: xen git://xenbits.xen.org/xen.git
Bug introduced: b43501451733193b265de30fd79a764363a2a473
Bug not present: eef83fd2af0d4c78afec34c199c977fc97d8a0b3
Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/120707/
commit b43501451733193b265de30fd79a764363a2a473
Author: Doug Goldstein <cardoe@cardoe.com>
Date: Mon Mar 12 23:06:51 2018 -0500
tools: detect appropriate debug optimization level
When building debug use -Og as the optimization level if its available,
otherwise retain the use of -O0. -Og has been added by GCC to enable all
optimizations that to not affect debugging while retaining full
debugability.
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
For bisection revision-tuple graph see:
http://logs.test-lab.xenproject.org/osstest/results/bisect/xen-unstable-smoke/build-arm64-xsm.xen-build.html
Revision IDs in each graph node refer, respectively, to the Trees above.
----------------------------------------
Running cs-bisection-step --graph-out=/home/logs/results/bisect/xen-unstable-smoke/build-arm64-xsm.xen-build --summary-out=tmp/120707.bisection-summary --basis-template=120679 --blessings=real,real-bisect xen-unstable-smoke build-arm64-xsm xen-build
Searching for failure / basis pass:
120699 fail [host=laxton1] / 120679 ok.
Failure / basis pass flights: 120699 / 120679
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
Latest 5c3fdee026a204a59cb392e43a313ab558de9682 a7313da7f7767984172873adf645eff9bd667bda
Basis pass 5c3fdee026a204a59cb392e43a313ab558de9682 eef83fd2af0d4c78afec34c199c977fc97d8a0b3
Generating revisions with ./adhoc-revtuple-generator git://xenbits.xen.org/qemu-xen.git#5c3fdee026a204a59cb392e43a313ab558de9682-5c3fdee026a204a59cb392e43a313ab558de9682 git://xenbits.xen.org/xen.git#eef83fd2af0d4c78afec34c199c977fc97d8a0b3-a7313da7f7767984172873adf645eff9bd667bda
Loaded 1001 nodes in revision graph
Searching for test results:
120689 fail 5c3fdee026a204a59cb392e43a313ab558de9682 a7313da7f7767984172873adf645eff9bd667bda
120679 pass 5c3fdee026a204a59cb392e43a313ab558de9682 eef83fd2af0d4c78afec34c199c977fc97d8a0b3
120687 pass 5c3fdee026a204a59cb392e43a313ab558de9682 eef83fd2af0d4c78afec34c199c977fc97d8a0b3
120685 fail 5c3fdee026a204a59cb392e43a313ab558de9682 a7313da7f7767984172873adf645eff9bd667bda
120688 fail 5c3fdee026a204a59cb392e43a313ab558de9682 a7313da7f7767984172873adf645eff9bd667bda
120693 fail 5c3fdee026a204a59cb392e43a313ab558de9682 b43501451733193b265de30fd79a764363a2a473
120701 fail 5c3fdee026a204a59cb392e43a313ab558de9682 b43501451733193b265de30fd79a764363a2a473
120696 pass 5c3fdee026a204a59cb392e43a313ab558de9682 eef83fd2af0d4c78afec34c199c977fc97d8a0b3
120699 fail 5c3fdee026a204a59cb392e43a313ab558de9682 a7313da7f7767984172873adf645eff9bd667bda
120703 pass 5c3fdee026a204a59cb392e43a313ab558de9682 eef83fd2af0d4c78afec34c199c977fc97d8a0b3
120707 fail 5c3fdee026a204a59cb392e43a313ab558de9682 b43501451733193b265de30fd79a764363a2a473
Searching for interesting versions
Result found: flight 120679 (pass), for basis pass
Result found: flight 120685 (fail), for basis failure
Repro found: flight 120687 (pass), for basis pass
Repro found: flight 120688 (fail), for basis failure
0 revisions at 5c3fdee026a204a59cb392e43a313ab558de9682 eef83fd2af0d4c78afec34c199c977fc97d8a0b3
No revisions left to test, checking graph state.
Result found: flight 120679 (pass), for last pass
Result found: flight 120693 (fail), for first failure
Repro found: flight 120696 (pass), for last pass
Repro found: flight 120701 (fail), for first failure
Repro found: flight 120703 (pass), for last pass
Repro found: flight 120707 (fail), for first failure
*** Found and reproduced problem changeset ***
Bug is in tree: xen git://xenbits.xen.org/xen.git
Bug introduced: b43501451733193b265de30fd79a764363a2a473
Bug not present: eef83fd2af0d4c78afec34c199c977fc97d8a0b3
Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/120707/
commit b43501451733193b265de30fd79a764363a2a473
Author: Doug Goldstein <cardoe@cardoe.com>
Date: Mon Mar 12 23:06:51 2018 -0500
tools: detect appropriate debug optimization level
When building debug use -Og as the optimization level if its available,
otherwise retain the use of -O0. -Og has been added by GCC to enable all
optimizations that to not affect debugging while retaining full
debugability.
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
Revision graph left in /home/logs/results/bisect/xen-unstable-smoke/build-arm64-xsm.xen-build.{dot,ps,png,html,svg}.
----------------------------------------
120707: tolerable ALL FAIL
flight 120707 xen-unstable-smoke real-bisect [real]
http://logs.test-lab.xenproject.org/osstest/logs/120707/
Failures :-/ but no regressions.
Tests which did not succeed,
including tests which could not be run:
build-arm64-xsm 6 xen-build fail baseline untested
jobs:
build-arm64-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
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-03-14 2:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 2:29 osstest service owner [this message]
2018-03-14 7:59 ` [xen-unstable-smoke bisection] complete build-arm64-xsm Jan Beulich
2018-03-14 9:01 ` Andrew Cooper
2018-03-14 10:54 ` Wei Liu
2018-03-14 13:42 ` Doug Goldstein
-- strict thread matches above, loose matches on Subject: below --
2023-06-08 7:13 osstest service owner
2022-09-30 0:06 osstest service owner
2021-07-06 20:34 osstest service owner
2021-05-18 19:57 osstest service owner
2021-02-02 4:17 osstest service owner
2021-01-15 20:46 osstest service owner
2020-10-24 2:26 osstest service owner
2020-05-29 15:11 osstest service owner
2019-05-21 18:46 osstest service owner
2018-10-09 21:55 osstest service owner
2018-04-13 1:17 osstest service owner
2018-04-06 1:15 osstest service owner
2018-03-08 7:03 osstest service owner
2018-01-27 3:32 osstest service owner
2018-01-25 21:47 osstest service owner
2018-01-17 2:07 osstest service owner
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=E1evwAL-0001ri-7m@osstest.test-lab.xenproject.org \
--to=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xenproject.org \
/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).