From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [rumprun test] 120818: regressions - FAIL
Date: Sat, 17 Mar 2018 12:33:19 +0000 [thread overview]
Message-ID: <osstest-120818-mainreport@xen.org> (raw)
flight 120818 rumprun real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120818/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumprun 6 rumprun-build fail REGR. vs. 106754
build-i386-rumprun 6 rumprun-build fail REGR. vs. 106754
Tests which did not succeed, but are not blocking:
test-amd64-i386-rumprun-i386 1 build-check(1) blocked n/a
test-amd64-amd64-rumprun-amd64 1 build-check(1) blocked n/a
version targeted for testing:
rumprun 94bdf32ac57b84c1b42150d21f0ad79b3b5dd99c
baseline version:
rumprun c7f2f016becc1cd0e85da6e1b25a8e7f9fb2aa74
Last test of basis 106754 2017-03-18 04:21:25 Z 364 days
Testing same since 120360 2018-03-09 04:19:20 Z 8 days 6 attempts
------------------------------------------------------------
People who touched revisions under test:
Kent McLeod <kent-mcleod@users.noreply.github.com>
Kent McLeod <Kent.Mcleod@data61.csiro.au>
Naja Melan <najamelan@autistici.org>
Sebastian Wicki <gandro@gmx.net>
Wei Liu <wei.liu2@citrix.com>
jobs:
build-amd64 pass
build-i386 pass
build-amd64-pvops pass
build-i386-pvops pass
build-amd64-rumprun fail
build-i386-rumprun fail
test-amd64-amd64-rumprun-amd64 blocked
test-amd64-i386-rumprun-i386 blocked
------------------------------------------------------------
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
Not pushing.
------------------------------------------------------------
commit 94bdf32ac57b84c1b42150d21f0ad79b3b5dd99c
Merge: 8fe40c8 b3c1033
Author: Kent McLeod <kent-mcleod@users.noreply.github.com>
Date: Fri Feb 16 09:15:45 2018 +1100
Merge pull request #118 from kent-mcleod/stretch-linking-defaultpie
Fix linking on Debian Stretch (gcc-6)
commit b3c1033b090b65e8e86999ddd063c174502aa3f0
Author: Kent McLeod <Kent.Mcleod@data61.csiro.au>
Date: Wed Feb 14 16:43:16 2018 +1100
Add further -no-pie checks to Rumprun build tools
This builds upon the previous commit to add -no-pie anywhere the
relocatable flag (-Wl,-r) is used to handle compilers that enable -pie
by default (Such as Debian Stretch).
commit 8fe40c84edddfbf472b4a7cce960df749701174c
Merge: c7f2f01 685f4ab
Author: Sebastian Wicki <gandro@gmx.net>
Date: Fri Jan 5 15:04:18 2018 +0100
Merge pull request #112 from najamelan/bugfix/gcc7-fallthrough
Add the -Wimplicit-fallthrough=0 flag to allow compiling with GCC7
commit 685f4ab3b74b6f1e1b40bdd3d2c42efa44bf385d
Author: Naja Melan <najamelan@autistici.org>
Date: Thu Jan 4 16:07:46 2018 +0000
Make the disabling of the fallthrough warning dependent on GCC version
This should prevent older gcc versions from choking on unknown argument.
I have not tested this, just wrote the code directly on github. Use with caution.
commit 34056451174e8722b972229fefc1bf9e0b89a7da
Author: Naja Melan <najamelan@autistici.org>
Date: Wed Jan 3 18:57:50 2018 +0000
Add the -Wimplicit-fallthrough=0 flag to allow compiling with GCC7
GCC7 comes with a new warning "implicit-fallthrough" which will prevent building the netbsd-src.
For more information: https://dzone.com/articles/implicit-fallthrough-in-gcc-7
commit 35d81194b7feb75d20af3ba4fdb45ea76230852f
Author: Wei Liu <wei.liu2@citrix.com>
Date: Wed Jun 7 16:30:00 2017 +0100
Fix linking on Debian Stretch
Provide cc-option. Use that to check if -no-pie is available and
append it when necessary.
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2018-03-17 12:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-120818-mainreport@xen.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).