branch xen-4.3-testing
xen branch xen-4.3-testing
job build-amd64
test xen-build
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-4.3-testing.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-4.3-testing.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: 2ddcdd96a0996fe755c6a9ba08182925c57ea412
Bug not present: 998424e33db121270690586320e899a03c88b4aa
commit 2ddcdd96a0996fe755c6a9ba08182925c57ea412
Author: Ian Jackson <ian.jack...@eu.citrix.com>
Date: Thu Feb 27 17:46:49 2014 +0000
tools/console: xenconsole tolerate tty errors
Since 28d386fc4341 (XSA-57), libxl writes an empty value for the
console tty node, with read-only permission for the guest, when
setting up pv console "frontends". (The actual tty value is later set
by xenconsoled.) Writing an empty node is not strictly necessary to
stop the frontend from writing dangerous values here, but it is a good
belt-and-braces approach.
Unfortunately this confuses xenconsole. It reads the empty value, and
tries to open it as the tty. xenconsole then exits.
Fix this by having xenconsole treat an empty value the same way as no
value at all.
Also, make the error opening the tty be nonfatal: we just print a
warning, but do not exit. I think this is helpful in theoretical
situations where xenconsole is racing with libxl and/or xenconsoled.
Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
Acked-by: Ian Campbell <ian.campb...@citrix.com>
CC: George Dunlap <george.dun...@eu.citrix.com>
---
v2: Combine two conditions and move the free
(cherry picked from commit 39ba2989b10b6a1852e253b204eb010f8e7026f1)
(cherry picked from commit 7b161be2e51c519754ac4435d63c8fc03db606ec)
Conflicts:
tools/console/client/main.c
Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
For bisection revision-tuple graph see:
http://logs.test-lab.xenproject.org/osstest/results/bisect/xen-4.3-testing/build-amd64.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-4.3-testing/build-amd64.xen-build
--summary-out=tmp/63184.bisection-summary --basis-template=62742
--blessings=real,real-bisect xen-4.3-testing build-amd64 xen-build
Searching for failure / basis pass:
63098 fail [host=godello0] / 62742 [host=nocera0] 62392 [host=nocera0] 62208
[host=nocera0] 62128 [host=nocera0] 62056 [host=nocera0] 61961 [host=nocera0]
61790 [host=nocera0] 60742 [host=nocera0] 60701 [host=nocera1] 60674
[host=nocera0] 60151 ok.
Failure / basis pass flights: 63098 / 60151
(tree with no url: seabios)
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-4.3-testing.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-4.3-testing.git
Tree: xen git://xenbits.xen.org/xen.git
Latest 1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
b188780861662e8cf1847ec562799b32bb44f05e
8c5d8c049dad890965124ae4e169e274a693c8fa
Basis pass e1db2596d7c5f8be876481148d407f0cb207b494
efae5e0f79f77c77720185a0d8a49f3ba49071e7
d7ab3a1c1cc245dc0683bb937467c27141754053
Generating revisions with ./adhoc-revtuple-generator
git://xenbits.xen.org/staging/qemu-xen-4.3-testing.git#e1db2596d7c5f8be876481148d407f0cb207b494-1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
git://xenbits.xen.org/staging/qemu-upstream-4.3-testing.git#efae5e0f79f77c77720185a0d8a49f3ba49071e7-b188780861662e8cf1847ec562799b32bb44f05e
git://xenbits.xen.org/xen.git#d7ab3a1c1cc245dc0683bb937467c27141754053-8c5d8c049dad890965124ae4e169e274a693c8fa
Loaded 4992 nodes in revision graph
Searching for test results:
60193 [host=nocera0]
60151 pass e1db2596d7c5f8be876481148d407f0cb207b494
efae5e0f79f77c77720185a0d8a49f3ba49071e7
d7ab3a1c1cc245dc0683bb937467c27141754053
60394 [host=italia1]
60674 [host=nocera0]
60702 [host=nocera1]
60701 [host=nocera1]
60737 [host=pinot0]
60742 [host=nocera0]
61140 [host=nocera0]
61790 [host=nocera0]
61961 [host=nocera0]
61960 [host=nocera0]
62128 [host=nocera0]
62056 [host=nocera0]
62208 [host=nocera0]
62307 [host=nocera0]
62392 [host=nocera0]
62742 [host=nocera0]
63150 fail 1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
b188780861662e8cf1847ec562799b32bb44f05e
8c5d8c049dad890965124ae4e169e274a693c8fa
63098 fail 1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
b188780861662e8cf1847ec562799b32bb44f05e
8c5d8c049dad890965124ae4e169e274a693c8fa
63143 pass e1db2596d7c5f8be876481148d407f0cb207b494
efae5e0f79f77c77720185a0d8a49f3ba49071e7
d7ab3a1c1cc245dc0683bb937467c27141754053
63154 pass e1db2596d7c5f8be876481148d407f0cb207b494
20c1b1812de98ed789d55e22a43a4700fb765596
116bbc6062cd90b98f746c3a058f4ec24347527d
63160 pass 1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
92dae02ba02166cfcce020cb71021a73903ada2f
13a30798d12e7a355173fe9cf149b3a4c6dc46b8
63163 pass 1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
b188780861662e8cf1847ec562799b32bb44f05e
f97021eb92e91db8032d600893a531863a18bd23
63168 pass 1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
b188780861662e8cf1847ec562799b32bb44f05e
998424e33db121270690586320e899a03c88b4aa
63172 fail 1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
b188780861662e8cf1847ec562799b32bb44f05e
2ddcdd96a0996fe755c6a9ba08182925c57ea412
63173 pass 1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
b188780861662e8cf1847ec562799b32bb44f05e
998424e33db121270690586320e899a03c88b4aa
63175 fail 1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
b188780861662e8cf1847ec562799b32bb44f05e
2ddcdd96a0996fe755c6a9ba08182925c57ea412
63179 pass 1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
b188780861662e8cf1847ec562799b32bb44f05e
998424e33db121270690586320e899a03c88b4aa
63184 fail 1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
b188780861662e8cf1847ec562799b32bb44f05e
2ddcdd96a0996fe755c6a9ba08182925c57ea412
Searching for interesting versions
Result found: flight 60151 (pass), for basis pass
Result found: flight 63098 (fail), for basis failure
Repro found: flight 63143 (pass), for basis pass
Repro found: flight 63150 (fail), for basis failure
0 revisions at 1e5099d596b6f7a977d4bc040a54edc2a6a3c6a4
b188780861662e8cf1847ec562799b32bb44f05e
998424e33db121270690586320e899a03c88b4aa
No revisions left to test, checking graph state.
Result found: flight 63168 (pass), for last pass
Result found: flight 63172 (fail), for first failure
Repro found: flight 63173 (pass), for last pass
Repro found: flight 63175 (fail), for first failure
Repro found: flight 63179 (pass), for last pass
Repro found: flight 63184 (fail), for first failure
*** Found and reproduced problem changeset ***
Bug is in tree: xen git://xenbits.xen.org/xen.git
Bug introduced: 2ddcdd96a0996fe755c6a9ba08182925c57ea412
Bug not present: 998424e33db121270690586320e899a03c88b4aa
commit 2ddcdd96a0996fe755c6a9ba08182925c57ea412
Author: Ian Jackson <ian.jack...@eu.citrix.com>
Date: Thu Feb 27 17:46:49 2014 +0000
tools/console: xenconsole tolerate tty errors
Since 28d386fc4341 (XSA-57), libxl writes an empty value for the
console tty node, with read-only permission for the guest, when
setting up pv console "frontends". (The actual tty value is later set
by xenconsoled.) Writing an empty node is not strictly necessary to
stop the frontend from writing dangerous values here, but it is a good
belt-and-braces approach.
Unfortunately this confuses xenconsole. It reads the empty value, and
tries to open it as the tty. xenconsole then exits.
Fix this by having xenconsole treat an empty value the same way as no
value at all.
Also, make the error opening the tty be nonfatal: we just print a
warning, but do not exit. I think this is helpful in theoretical
situations where xenconsole is racing with libxl and/or xenconsoled.
Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
Acked-by: Ian Campbell <ian.campb...@citrix.com>
CC: George Dunlap <george.dun...@eu.citrix.com>
---
v2: Combine two conditions and move the free
(cherry picked from commit 39ba2989b10b6a1852e253b204eb010f8e7026f1)
(cherry picked from commit 7b161be2e51c519754ac4435d63c8fc03db606ec)
Conflicts:
tools/console/client/main.c
Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
Revision graph left in
/home/logs/results/bisect/xen-4.3-testing/build-amd64.xen-build.{dot,ps,png,html}.
----------------------------------------
63184: tolerable ALL FAIL
flight 63184 xen-4.3-testing real-bisect [real]
http://logs.test-lab.xenproject.org/osstest/logs/63184/
Failures :-/ but no regressions.
Tests which did not succeed,
including tests which could not be run:
build-amd64 5 xen-build fail baseline untested
jobs:
build-amd64 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.xen.org
http://lists.xen.org/xen-devel
