All of lore.kernel.org
 help / color / mirror / Atom feed
From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [distros-debian-sid test] 71143: tolerable trouble: blocked/broken/fail/pass
Date: Mon, 3 Apr 2017 10:10:45 +0100	[thread overview]
Message-ID: <osstest-71143-mainreport@xen.org> (raw)

flight 71143 distros-debian-sid real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71143/

Failures :-/ but no regressions.

Regressions which are regarded as allowable (not blocking):
 test-amd64-i386-amd64-sid-netboot-pygrub 10 capture-logs(10) broken blocked in 71108
 test-amd64-i386-i386-sid-netboot-pvgrub 10 capture-logs(10) broken blocked in 71108
 test-armhf-armhf-armhf-sid-netboot-pygrub 9 debian-di-install fail blocked in 71108
 test-amd64-i386-amd64-sid-netboot-pygrub 9 debian-di-install fail blocked in 71108
 test-amd64-i386-i386-sid-netboot-pvgrub 9 debian-di-install fail blocked in 71108
 test-amd64-amd64-i386-sid-netboot-pygrub 9 debian-di-install fail blocked in 71108
 test-amd64-amd64-amd64-sid-netboot-pvgrub 9 debian-di-install fail blocked in 71108

Tests which did not succeed, but are not blocking:
 test-arm64-arm64-armhf-sid-netboot-pygrub  1 build-check(1)        blocked n/a
 build-arm64                   2 hosts-allocate               broken never pass
 build-arm64                   3 capture-logs                 broken never pass
 build-arm64-pvops             2 hosts-allocate               broken never pass
 build-arm64-pvops             3 capture-logs                 broken never pass

baseline version:
 flight               71108

jobs:
 build-amd64                                                  pass    
 build-arm64                                                  broken  
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-pvops                                            pass    
 build-arm64-pvops                                            broken  
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-amd64-sid-netboot-pvgrub                    fail    
 test-amd64-i386-i386-sid-netboot-pvgrub                      broken  
 test-amd64-i386-amd64-sid-netboot-pygrub                     broken  
 test-arm64-arm64-armhf-sid-netboot-pygrub                    blocked 
 test-armhf-armhf-armhf-sid-netboot-pygrub                    fail    
 test-amd64-amd64-i386-sid-netboot-pygrub                     fail    


------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images

Logs, config files, etc. are available at
    http://osstest.xs.citrite.net/~osstest/testlogs/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Push not applicable.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

                 reply	other threads:[~2017-04-03  9:10 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-71143-mainreport@xen.org \
    --to=citrix-osstest@xenproject.org \
    --cc=osstest-admin@xenproject.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 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.