From: Anthony PERARD <anthony.perard@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
Ian Jackson <ian.jackson@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [xen-unstable-coverity test] 140105: all pass - PUSHED
Date: Thu, 15 Aug 2019 13:50:42 +0100 [thread overview]
Message-ID: <20190815125042.GA25409@perard.uk.xensource.com> (raw)
In-Reply-To: <osstest-140105-mainreport@xen.org>
On Wed, Aug 14, 2019 at 09:52:31AM +0000, osstest service owner wrote:
> flight 140105 xen-unstable-coverity real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/140105/
>
> Perfect :-)
> All tests in this flight passed as required
> version targeted for testing:
> xen 243cc95d485846e35f5e2445fdaafe77c8c114d2
> baseline version:
> xen 762b9a2d990bba1f3aefe660cff0c37ad2e375bc
>
> Last test of basis 139934 2019-08-11 09:18:29 Z 3 days
> Testing same since 140105 2019-08-14 09:19:18 Z 0 days 1 attempts
I don't think the coverity upload is working.
On https://scan.coverity.com/projects/xenproject:
Last build analyzed: 3 months ago
And in the log [1], when the upload is done, there is:
Your build is already in the queue for analysis. Please wait till analysis finishes before uploading another build.
[1] http://logs.test-lab.xenproject.org/osstest/logs/140105/coverity-amd64/7.ts-coverity-upload.log
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-08-15 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 9:52 [Xen-devel] [xen-unstable-coverity test] 140105: all pass - PUSHED osstest service owner
2019-08-15 12:50 ` Anthony PERARD [this message]
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=20190815125042.GA25409@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=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 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).