xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, rumpkernel-builds@freelists.org,
	osstest-admin@xenproject.org
Subject: [rumpuserxen test] 59427: regressions - FAIL
Date: Sat, 11 Jul 2015 07:43:18 +0000	[thread overview]
Message-ID: <osstest-59427-mainreport@xen.org> (raw)

flight 59427 rumpuserxen real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59427/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-i386-pvops              5 kernel-build              fail REGR. vs. 33866
 build-amd64-rumpuserxen       5 rumpuserxen-build         fail REGR. vs. 33866
 build-i386                    5 xen-build                 fail REGR. vs. 33866

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-rumpuserxen-amd64  1 build-check(1)               blocked n/a
 test-amd64-i386-rumpuserxen-i386  1 build-check(1)               blocked  n/a
 build-i386-rumpuserxen        1 build-check(1)               blocked  n/a

version targeted for testing:
 rumpuserxen          3b91e44996ea6ae1276bce1cc44f38701c53ee6f
baseline version:
 rumpuserxen          30d72f3fc5e35cd53afd82c8179cc0e0b11146ad

Last test of basis    33866  2015-01-28 04:19:26 Z  164 days
Failing since         34129  2015-02-03 04:21:40 Z  158 days  113 attempts
Testing same since    50441  2015-04-15 20:51:55 Z   86 days   68 attempts

------------------------------------------------------------
People who touched revisions under test:
  Antti Kantee <pooka@iki.fi>
  Ian Jackson <Ian.Jackson@eu.citrix.com>
  Martin Lucina <martin@lucina.net>
  Wei Liu <liuw@liuw.name>

jobs:
 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   fail    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             fail    
 build-amd64-rumpuserxen                                      fail    
 build-i386-rumpuserxen                                       blocked 
 test-amd64-amd64-rumpuserxen-amd64                           blocked 
 test-amd64-i386-rumpuserxen-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.

(No revision log; it would be 535 lines long.)

                 reply	other threads:[~2015-07-11  7:43 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-59427-mainreport@xen.org \
    --to=osstest-admin@xenproject.org \
    --cc=rumpkernel-builds@freelists.org \
    --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 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).