[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-4.3-testing bisection] complete build-armhf
branch xen-4.3-testing xen branch xen-4.3-testing job build-armhf test xen-build 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.jackson@xxxxxxxxxxxxx> 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.Jackson@xxxxxxxxxxxxx> Acked-by: Ian Campbell <Ian.Campbell@xxxxxxxxxx> CC: George Dunlap <george.dunlap@xxxxxxxxxxxxx> --- 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.jackson@xxxxxxxxxxxxx> For bisection revision-tuple graph see: http://logs.test-lab.xenproject.org/osstest/results/bisect/xen-4.3-testing/build-armhf.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-armhf.xen-build --summary-out=tmp/63200.bisection-summary --basis-template=62742 --blessings=real,real-bisect xen-4.3-testing build-armhf xen-build Searching for failure / basis pass: 63098 fail [host=arndale-metrocentre] / 62742 [host=arndale-westfield] 62392 [host=arndale-lakeside] 62208 [host=arndale-lakeside] 62128 [host=arndale-westfield] 62056 [host=arndale-westfield] 61961 [host=arndale-westfield] 61790 [host=arndale-bluewater] 60742 [host=arndale-westfield] 60701 [host=arndale-bluewater] 60674 [host=arndale-bluewater] 60151 [host=cubietruck-braque] 58884 [host=arndale-westfield] 58848 [host=arndale-westfield] 58440 [host=arndale-westfield] 58404 ok. Failure / basis pass flights: 63098 / 58404 Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-4.3-testing.git Tree: xen git://xenbits.xen.org/xen.git Latest b188780861662e8cf1847ec562799b32bb44f05e 8c5d8c049dad890965124ae4e169e274a693c8fa Basis pass 447b1c5f24bb942f1b821e6a0e56e743dcffae84 9176955cb837ba0752ca7ca7a197c9c394468e9f Generating revisions with ./adhoc-revtuple-generator git://xenbits.xen.org/staging/qemu-upstream-4.3-testing.git#447b1c5f24bb942f1b821e6a0e56e743dcffae84-b188780861662e8cf1847ec562799b32bb44f05e git://xenbits.xen.org/xen.git#9176955cb837ba0752ca7ca7a197c9c394468e9f-8c5d8c049dad890965124ae4e169e274a693c8fa Loaded 2008 nodes in revision graph Searching for test results: 58440 [host=arndale-westfield] 58404 pass 447b1c5f24bb942f1b821e6a0e56e743dcffae84 9176955cb837ba0752ca7ca7a197c9c394468e9f 58848 [host=arndale-westfield] 58884 [host=arndale-westfield] 60151 [host=cubietruck-braque] 60674 [host=arndale-bluewater] 60701 [host=arndale-bluewater] 60742 [host=arndale-westfield] 61140 [host=arndale-bluewater] 61790 [host=arndale-bluewater] 61961 [host=arndale-westfield] 62128 [host=arndale-westfield] 62056 [host=arndale-westfield] 62208 [host=arndale-lakeside] 62392 [host=arndale-lakeside] 62742 [host=arndale-westfield] 63098 fail b188780861662e8cf1847ec562799b32bb44f05e 8c5d8c049dad890965124ae4e169e274a693c8fa 63192 pass a222654ebc3b2292d57e1b48aea2d57340983a6d f97021eb92e91db8032d600893a531863a18bd23 63193 pass b188780861662e8cf1847ec562799b32bb44f05e 998424e33db121270690586320e899a03c88b4aa 63195 fail b188780861662e8cf1847ec562799b32bb44f05e 2ddcdd96a0996fe755c6a9ba08182925c57ea412 63196 pass b188780861662e8cf1847ec562799b32bb44f05e 998424e33db121270690586320e899a03c88b4aa 63197 fail b188780861662e8cf1847ec562799b32bb44f05e 2ddcdd96a0996fe755c6a9ba08182925c57ea412 63198 pass b188780861662e8cf1847ec562799b32bb44f05e 998424e33db121270690586320e899a03c88b4aa 63200 fail b188780861662e8cf1847ec562799b32bb44f05e 2ddcdd96a0996fe755c6a9ba08182925c57ea412 63185 pass 447b1c5f24bb942f1b821e6a0e56e743dcffae84 9176955cb837ba0752ca7ca7a197c9c394468e9f 63187 fail b188780861662e8cf1847ec562799b32bb44f05e 8c5d8c049dad890965124ae4e169e274a693c8fa 63189 pass 20c1b1812de98ed789d55e22a43a4700fb765596 dea3fd1e945de74154e74989623a4272f43338fe 63190 pass 20c1b1812de98ed789d55e22a43a4700fb765596 3bcb2c062a02e3c45d3f87478d2cbe1a134d395c Searching for interesting versions Result found: flight 58404 (pass), for basis pass Result found: flight 63098 (fail), for basis failure Repro found: flight 63185 (pass), for basis pass Repro found: flight 63187 (fail), for basis failure 0 revisions at b188780861662e8cf1847ec562799b32bb44f05e 998424e33db121270690586320e899a03c88b4aa No revisions left to test, checking graph state. Result found: flight 63193 (pass), for last pass Result found: flight 63195 (fail), for first failure Repro found: flight 63196 (pass), for last pass Repro found: flight 63197 (fail), for first failure Repro found: flight 63198 (pass), for last pass Repro found: flight 63200 (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.jackson@xxxxxxxxxxxxx> 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.Jackson@xxxxxxxxxxxxx> Acked-by: Ian Campbell <Ian.Campbell@xxxxxxxxxx> CC: George Dunlap <george.dunlap@xxxxxxxxxxxxx> --- 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.jackson@xxxxxxxxxxxxx> Revision graph left in /home/logs/results/bisect/xen-4.3-testing/build-armhf.xen-build.{dot,ps,png,html}. ---------------------------------------- 63200: tolerable ALL FAIL flight 63200 xen-4.3-testing real-bisect [real] http://logs.test-lab.xenproject.org/osstest/logs/63200/ Failures :-/ but no regressions. Tests which did not succeed, including tests which could not be run: build-armhf 5 xen-build fail baseline untested jobs: build-armhf 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@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |