From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [Xen-devel] [xen-unstable-smoke bisection] complete build-arm64-xsm
Date: Tue, 21 May 2019 18:46:09 +0000 [thread overview]
Message-ID: <E1hT9m5-0000TK-4Y@osstest.test-lab.xenproject.org> (raw)
Message-ID: <20190521184609.X6wNYftNvCPUy7bPGVFFURMEfGgownLjg_4i7RFOevA@z> (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: 03957f58db8942d61f4889b6924e39d3b27a9e43
Bug not present: 57d87ee3a5d10cdba972eec3a54cd971fec1b8d2
Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136714/
commit 03957f58db8942d61f4889b6924e39d3b27a9e43
Author: Julien Grall <julien.grall@arm.com>
Date: Tue May 14 13:24:38 2019 +0100
xen/const: Extend the existing macro BIT to take a suffix in parameter
Arm currently provides two macro BIT and BIT_ULL that are only usable
in C and return respectively unsigned long and unsigned long long.
Extending the macros to deal with assembly would be a nice benefits as
it could replace the common pattern to define fields (AC(1, sfx) << X)
easier to read.
Rather than extending the two macros, it was decided to drop BIT_ULL()
and extend the macro BIT() to take a suffix (e.g U, UL, ULL) in
parameter. This would allow to use different suffix without having to
define new macros.
The new extend macro is now moved in include/xen/const.h so it can be
used by anyone in Xen and also avoid to include bitops.h in assembly
code.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
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/136714.bisection-summary --basis-template=136665 --blessings=real,real-bisect xen-unstable-smoke build-arm64-xsm xen-build
Searching for failure / basis pass:
136687 fail [host=laxton0] / 136665 ok.
Failure / basis pass flights: 136687 / 136665
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
Latest 9cca02d8ffc23e9688a971d858e4ffdff5389b11 b915f57a49bc12e9f5fb60ce604772b09777ff0d
Basis pass 9cca02d8ffc23e9688a971d858e4ffdff5389b11 91f86f8634f99abd8f242943e62452211a09fa0a
Generating revisions with ./adhoc-revtuple-generator git://xenbits.xen.org/qemu-xen.git#9cca02d8ffc23e9688a971d858e4ffdff5389b11-9cca02d8ffc23e9688a971d858e4ffdff5389b11 git://xenbits.xen.org/xen.git#91f86f8634f99abd8f242943e62452211a09fa0a-b915f57a49bc12e9f5fb60ce604772b09777ff0d
Loaded 1001 nodes in revision graph
Searching for test results:
136705 pass 9cca02d8ffc23e9688a971d858e4ffdff5389b11 57d87ee3a5d10cdba972eec3a54cd971fec1b8d2
136665 pass 9cca02d8ffc23e9688a971d858e4ffdff5389b11 91f86f8634f99abd8f242943e62452211a09fa0a
136700 fail 9cca02d8ffc23e9688a971d858e4ffdff5389b11 b915f57a49bc12e9f5fb60ce604772b09777ff0d
136687 fail 9cca02d8ffc23e9688a971d858e4ffdff5389b11 b915f57a49bc12e9f5fb60ce604772b09777ff0d
136710 fail 9cca02d8ffc23e9688a971d858e4ffdff5389b11 03957f58db8942d61f4889b6924e39d3b27a9e43
136702 fail 9cca02d8ffc23e9688a971d858e4ffdff5389b11 7ad0e780857728724e59859dcc422404d4ed0c46
136708 fail 9cca02d8ffc23e9688a971d858e4ffdff5389b11 03957f58db8942d61f4889b6924e39d3b27a9e43
136698 pass 9cca02d8ffc23e9688a971d858e4ffdff5389b11 91f86f8634f99abd8f242943e62452211a09fa0a
136704 fail 9cca02d8ffc23e9688a971d858e4ffdff5389b11 03957f58db8942d61f4889b6924e39d3b27a9e43
136709 pass 9cca02d8ffc23e9688a971d858e4ffdff5389b11 57d87ee3a5d10cdba972eec3a54cd971fec1b8d2
136714 fail 9cca02d8ffc23e9688a971d858e4ffdff5389b11 03957f58db8942d61f4889b6924e39d3b27a9e43
136711 pass 9cca02d8ffc23e9688a971d858e4ffdff5389b11 57d87ee3a5d10cdba972eec3a54cd971fec1b8d2
Searching for interesting versions
Result found: flight 136665 (pass), for basis pass
Result found: flight 136687 (fail), for basis failure
Repro found: flight 136698 (pass), for basis pass
Repro found: flight 136700 (fail), for basis failure
0 revisions at 9cca02d8ffc23e9688a971d858e4ffdff5389b11 57d87ee3a5d10cdba972eec3a54cd971fec1b8d2
No revisions left to test, checking graph state.
Result found: flight 136705 (pass), for last pass
Result found: flight 136708 (fail), for first failure
Repro found: flight 136709 (pass), for last pass
Repro found: flight 136710 (fail), for first failure
Repro found: flight 136711 (pass), for last pass
Repro found: flight 136714 (fail), for first failure
*** Found and reproduced problem changeset ***
Bug is in tree: xen git://xenbits.xen.org/xen.git
Bug introduced: 03957f58db8942d61f4889b6924e39d3b27a9e43
Bug not present: 57d87ee3a5d10cdba972eec3a54cd971fec1b8d2
Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/136714/
commit 03957f58db8942d61f4889b6924e39d3b27a9e43
Author: Julien Grall <julien.grall@arm.com>
Date: Tue May 14 13:24:38 2019 +0100
xen/const: Extend the existing macro BIT to take a suffix in parameter
Arm currently provides two macro BIT and BIT_ULL that are only usable
in C and return respectively unsigned long and unsigned long long.
Extending the macros to deal with assembly would be a nice benefits as
it could replace the common pattern to define fields (AC(1, sfx) << X)
easier to read.
Rather than extending the two macros, it was decided to drop BIT_ULL()
and extend the macro BIT() to take a suffix (e.g U, UL, ULL) in
parameter. This would allow to use different suffix without having to
define new macros.
The new extend macro is now moved in include/xen/const.h so it can be
used by anyone in Xen and also avoid to include bitops.h in assembly
code.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Revision graph left in /home/logs/results/bisect/xen-unstable-smoke/build-arm64-xsm.xen-build.{dot,ps,png,html,svg}.
----------------------------------------
136714: tolerable ALL FAIL
flight 136714 xen-unstable-smoke real-bisect [real]
http://logs.test-lab.xenproject.org/osstest/logs/136714/
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:[~2019-05-21 18:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 18:46 osstest service owner [this message]
2019-05-21 18:46 ` [Xen-devel] [xen-unstable-smoke bisection] complete build-arm64-xsm osstest service owner
-- 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
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-14 2:29 osstest service owner
2018-03-14 7:59 ` Jan Beulich
2018-03-14 9:01 ` Andrew Cooper
2018-03-14 10:54 ` Wei Liu
2018-03-14 13:42 ` Doug Goldstein
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=E1hT9m5-0000TK-4Y@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).