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-snapshot test] 67732: trouble: blocked/broken/pass
Date: Tue, 20 Sep 2016 14:36:35 +0100	[thread overview]
Message-ID: <osstest-67732-mainreport@xen.org> (raw)

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

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-i386                    3 host-install(3)         broken REGR. vs. 67704
 build-amd64                   3 host-install(3)         broken REGR. vs. 67704
 build-armhf                   3 host-install(3)         broken REGR. vs. 67704

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-armhf-daily-netboot-pygrub  1 build-check(1)      blocked n/a
 test-amd64-i386-amd64-weekly-netinst-pygrub  1 build-check(1)      blocked n/a
 test-amd64-amd64-amd64-current-netinst-pygrub  1 build-check(1)    blocked n/a
 test-amd64-i386-amd64-current-netinst-pygrub  1 build-check(1)     blocked n/a
 test-amd64-amd64-amd64-daily-netboot-pvgrub  1 build-check(1)      blocked n/a
 test-amd64-i386-i386-daily-netboot-pvgrub  1 build-check(1)        blocked n/a
 test-amd64-i386-i386-weekly-netinst-pygrub  1 build-check(1)       blocked n/a
 test-amd64-i386-amd64-daily-netboot-pygrub  1 build-check(1)       blocked n/a
 test-amd64-amd64-i386-daily-netboot-pygrub  1 build-check(1)       blocked n/a
 test-amd64-i386-i386-current-netinst-pygrub  1 build-check(1)      blocked n/a
 test-amd64-amd64-i386-weekly-netinst-pygrub  1 build-check(1)      blocked n/a
 test-amd64-amd64-i386-current-netinst-pygrub  1 build-check(1)     blocked n/a
 test-amd64-amd64-amd64-weekly-netinst-pygrub  1 build-check(1)     blocked n/a

baseline version:
 flight               67704

jobs:
 build-amd64                                                  broken  
 build-armhf                                                  broken  
 build-i386                                                   broken  
 build-amd64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-amd64-daily-netboot-pvgrub                  blocked 
 test-amd64-i386-i386-daily-netboot-pvgrub                    blocked 
 test-amd64-i386-amd64-daily-netboot-pygrub                   blocked 
 test-armhf-armhf-armhf-daily-netboot-pygrub                  blocked 
 test-amd64-amd64-i386-daily-netboot-pygrub                   blocked 
 test-amd64-amd64-amd64-current-netinst-pygrub                blocked 
 test-amd64-i386-amd64-current-netinst-pygrub                 blocked 
 test-amd64-amd64-i386-current-netinst-pygrub                 blocked 
 test-amd64-i386-i386-current-netinst-pygrub                  blocked 
 test-amd64-amd64-amd64-weekly-netinst-pygrub                 blocked 
 test-amd64-i386-amd64-weekly-netinst-pygrub                  blocked 
 test-amd64-amd64-i386-weekly-netinst-pygrub                  blocked 
 test-amd64-i386-i386-weekly-netinst-pygrub                   blocked 


------------------------------------------------------------
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:[~2016-09-20 13:36 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-67732-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.