All of lore.kernel.org
 help / color / mirror / Atom feed
From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org,
	royger@FreeBSD.org
Subject: [freebsd-master test] 128816: regressions - trouble: blocked/broken
Date: Mon, 15 Oct 2018 12:15:24 +0000	[thread overview]
Message-ID: <osstest-128816-mainreport@xen.org> (raw)

flight 128816 freebsd-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128816/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64-freebsd             <job status>                 broken
 build-amd64-freebsd           6 host-build-prep          fail REGR. vs. 128497

Tests which did not succeed, but are not blocking:
 build-amd64-freebsd-again     1 build-check(1)               blocked  n/a
 build-amd64-xen-freebsd       1 build-check(1)               blocked  n/a

version targeted for testing:
 freebsd              891833d897fdc770f91a1699fe94b8ea776eb35a
baseline version:
 freebsd              c0b412ce93b9d3ee750e5f262b50e64c52d300cc

Last test of basis   128497  2018-10-08 09:19:52 Z    7 days
Failing since        128582  2018-10-10 09:19:25 Z    5 days    3 attempts
Testing same since   128816  2018-10-15 09:19:04 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  0mp <0mp@FreeBSD.org>
  allanjude <allanjude@FreeBSD.org>
  br <br@FreeBSD.org>
  brooks <brooks@FreeBSD.org>
  bz <bz@FreeBSD.org>
  des <des@FreeBSD.org>
  egypcio <egypcio@FreeBSD.org>
  emaste <emaste@FreeBSD.org>
  erj <erj@FreeBSD.org>
  gjb <gjb@FreeBSD.org>
  hselasky <hselasky@FreeBSD.org>
  jhb <jhb@FreeBSD.org>
  jkim <jkim@FreeBSD.org>
  jtl <jtl@FreeBSD.org>
  kevans <kevans@FreeBSD.org>
  kib <kib@FreeBSD.org>
  mav <mav@FreeBSD.org>
  mjg <mjg@FreeBSD.org>
  mw <mw@FreeBSD.org>
  np <np@FreeBSD.org>
  nwhitehorn <nwhitehorn@FreeBSD.org>
  peter <peter@FreeBSD.org>
  rmacklem <rmacklem@FreeBSD.org>
  shurd <shurd@FreeBSD.org>
  trasz <trasz@FreeBSD.org>
  tsoome <tsoome@FreeBSD.org>
  yuripv <yuripv@FreeBSD.org>

jobs:
 build-amd64-freebsd-again                                    blocked 
 build-amd64-freebsd                                          broken  
 build-amd64-xen-freebsd                                      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

broken-job build-amd64-freebsd broken

Not pushing.

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

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

                 reply	other threads:[~2018-10-15 12:15 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-128816-mainreport@xen.org \
    --to=osstest-admin@xenproject.org \
    --cc=royger@FreeBSD.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 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.