From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org
Subject: [ovmf test] 181008: tolerable FAIL - PUSHED
Date: Tue, 30 May 2023 08:28:49 +0000 [thread overview]
Message-ID: <osstest-181008-mainreport@xen.org> (raw)
flight 181008 ovmf real [real]
flight 181010 ovmf real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/181008/
http://logs.test-lab.xenproject.org/osstest/logs/181010/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qemuu-ovmf-amd64 20 guest-start/debianhvm.repeat fail pass in 181010-retest
version targeted for testing:
ovmf 9d9761af50e538d983e00b1cb2d0ffcee261e552
baseline version:
ovmf 1034d223f8cc6bf8b9b86c57e564753cdad46f88
Last test of basis 181004 2023-05-29 18:15:27 Z 0 days
Testing same since 181008 2023-05-30 03:42:25 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Nickle Wang <nicklew@nvidia.com>
jobs:
build-amd64-xsm pass
build-i386-xsm pass
build-amd64 pass
build-i386 pass
build-amd64-libvirt pass
build-i386-libvirt pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 fail
test-amd64-i386-xl-qemuu-ovmf-amd64 pass
------------------------------------------------------------
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
Pushing revision :
To xenbits.xen.org:/home/xen/git/osstest/ovmf.git
1034d223f8..9d9761af50 9d9761af50e538d983e00b1cb2d0ffcee261e552 -> xen-tested-master
reply other threads:[~2023-05-30 8:29 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-181008-mainreport@xen.org \
--to=osstest-admin@xenproject.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.