From: xen.org <Ian.Jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com, rumpkernel-builds@lists.sourceforge.net
Cc: ian.jackson@eu.citrix.com
Subject: [rumpuserxen test] 33416: regressions - FAIL
Date: Thu, 15 Jan 2015 07:28:05 +0000 [thread overview]
Message-ID: <osstest-33416-mainreport@xen.org> (raw)
flight 33416 rumpuserxen real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33416/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-rumpuserxen-amd64 8 guest-start fail REGR. vs. 33401
version targeted for testing:
rumpuserxen ec3b62146d52e5deab349b00c6e768937d39a01f
baseline version:
rumpuserxen 1e71553faec32af113f1d91c8331341eed320ea5
------------------------------------------------------------
People who touched revisions under test:
Antti Kantee <pooka@iki.fi>
Martin Lucina <martin@lucina.net>
------------------------------------------------------------
jobs:
build-amd64 pass
build-i386 pass
build-amd64-pvops pass
build-i386-pvops pass
build-amd64-rumpuserxen pass
build-i386-rumpuserxen pass
test-amd64-amd64-rumpuserxen-amd64 fail
test-amd64-i386-rumpuserxen-i386 pass
------------------------------------------------------------
sg-report-flight on osstest.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images
Logs, config files, etc. are available at
http://www.chiark.greenend.org.uk/~xensrcts/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Not pushing.
------------------------------------------------------------
commit ec3b62146d52e5deab349b00c6e768937d39a01f
Author: Antti Kantee <pooka@iki.fi>
Date: Tue Jan 13 18:26:15 2015 +0000
pull in new buildrump.sh and rumpsrc (openssl 1.0.1k)
commit e858a76fe81e8fda2efcba025494b59747143a64
Author: Martin Lucina <martin@lucina.net>
Date: Tue Jan 13 19:05:09 2015 +0100
rumpconfig: Enable deconfig for network interfaces
Enable deconfig of network interaces, including dhcp. Current tests show
that issue #14 appears to be fixed, so this should be good to go.
Signed-off-by: Martin Lucina <martin@lucina.net>
commit 5c716e22bdb0d6f62e22b6ad97dd7048c29db4ca
Author: Martin Lucina <martin@lucina.net>
Date: Tue Jan 13 18:20:32 2015 +0100
Make initial stack setup consistent with per-thread stack setup
Push an "end of backtrace" marker onto the stack and zero BP. For x86_64
additionally push an extra 0 to ensure correct stack alignment as per
the ABI.
Signed-off-by: Martin Lucina <martin@lucina.net>
commit 97afb0013eeb4eb28bcd173bcc83c9c9163c5bdd
Author: Martin Lucina <martin@lucina.net>
Date: Mon Jan 12 15:20:00 2015 +0100
Correct x86-64 stack alignment at thread entry (fixes #18)
The x86-64 ABI mandates in section 3.2.2 that (%rsp + 8) is always a
multiple of 16 when control is transferred to a function entry point. We
did not correctly implement this convention which resulted in broken
alignment for stack variables, and, following from that, SSE
instructions generated by GCC faulting due to bad alignment.
For the x86-32 version the alignment constraint appears to be[1] that
%esp must be a multiple of 16, this is already the case so no change is
made to x86-32.s.
[1] http://sourceforge.net/p/fbc/bugs/659/,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38496
Signed-off-by: Martin Lucina <martin@lucina.net>
next reply other threads:[~2015-01-15 7:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 7:28 xen.org [this message]
2015-01-15 17:54 ` [rumpuserxen test] 33416: regressions - FAIL Martin Lucina
2015-01-15 18:05 ` Ian Jackson
2015-01-15 18:24 ` Martin Lucina
2015-01-15 18:32 ` [Xen-devel] " Martin Lucina
2015-01-15 18:37 ` Ian Jackson
2015-01-16 10:22 ` [rumpuserxen test] 33434: tolerable FAIL - PUSHED xen.org
2015-01-16 11:17 ` [rumpuserxen test] 33416: regressions - FAIL [and 1 more messages] Ian Jackson
2015-01-16 14:45 ` Antti Kantee
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=osstest-33416-mainreport@xen.org \
--to=ian.jackson@eu.citrix.com \
--cc=rumpkernel-builds@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.