From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [linux test] 6540: regressions - trouble: broken/fail/pass
Date: Thu, 17 Mar 2011 12:50:24 +0000 [thread overview]
Message-ID: <osstest-6540-mainreport@xen.org> (raw)
flight 6540 linux real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/6540/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-amd64-win 3 host-install(3) broken
test-amd64-amd64-xl-win 3 host-install(3) broken
test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 6360
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-i386-rhel6hvm-intel 8 guest-saverestore fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-i386-i386-xl-win 13 guest-stop fail never pass
version targeted for testing:
linux 95ff89cb44546e2a9d688d67b1021cc929c5a716
baseline version:
linux 3d14ce7d7f75966641eda1c87f678ecdc72b8cf0
------------------------------------------------------------
People who touched revisions under test:
------------------------------------------------------------
jobs:
build-amd64 pass
build-i386 pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-amd64-i386-xl pass
test-i386-i386-xl pass
test-amd64-i386-rhel6hvm-amd fail
test-amd64-i386-xl-credit2 pass
test-amd64-i386-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-i386-i386-pair pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv pass
test-amd64-i386-win-vcpus1 fail
test-amd64-i386-xl-win-vcpus1 fail
test-amd64-amd64-win broken
test-amd64-i386-win fail
test-i386-i386-win fail
test-amd64-amd64-xl-win broken
test-i386-i386-xl-win fail
------------------------------------------------------------
sg-report-flight on woking.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 95ff89cb44546e2a9d688d67b1021cc929c5a716
Merge: dfd083b... 62d08dd...
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Wed Mar 16 07:25:50 2011 -0700
Merge remote-tracking branch 'ianc/for-jeremy/netback' into xen/next-2.6.32
* ianc/for-jeremy/netback:
xen: netback: handle incoming GSO SKBs which are not CHECKSUM_PARTIAL
Revert "xen: netback: Drop GSO SKBs which do not have csum_blank."
xen: netback: completely remove tx_queue_timer
xen: netback: Drop GSO SKBs which do not have csum_blank.
xen: netback: Re-factor net_tx_action_dealloc() slightly.
xen: netback: Add a missing test to tx_work_todo.
xen: netback: Remove the 500ms timeout to restart the netif queue.
xen: netback: Don't count packets we don't actually receive.
xen: netback: Re-define PKT_PROT_LEN to be bigger.
reply other threads:[~2011-03-17 12:50 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-6540-mainreport@xen.org \
--to=ian.jackson@eu.citrix.com \
--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.