DPDK CI discussions
 help / color / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 493] Failures reported by Intel CI for series 10551
Date: Fri, 26 Jun 2020 13:37:34 +0000
Message-ID: <bug-493-149@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=493

            Bug ID: 493
           Summary: Failures reported by Intel CI for series 10551
           Product: lab
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: job scripts
          Assignee: ci@dpdk.org
          Reporter: lylavoie@iol.unh.edu
                CC: dpdklab@iol.unh.edu
  Target Milestone: ---

Actively being worked on the ci@dpdk.org email list, creating a bug here for
tracking...

####################################################################
####################################################################
From Zhaoyan Chen

Hi, David,

For your question, "Is it normal to see all patches with the exact same test
report?"
Yes, we always test a series, rather than a single patch. You can see the exact
same report
on any patch in a series. (it's convenient, you don't need backward to search
the header of the series, then check result)

" One thing that comes to mind, do we have dpdk headers installed system-
> wide on the Intel CI server(s)?"

Sure, we do. We don't see any problem on other patch compilation, so far. but
it's strange
that your V2 and V3 is same, but v3 test is failed. (code base is same). So I
will try to re-run
your series(v3), and check what's changed on CI system between the 2 days. Is
that helpful?

Regards,
Zhaoyan Chen


####################################################################
####################################################################
From David Marchand

> Hi, David,
>
> For your question, "Is it normal to see all patches with the exact same test
> report?"
> Yes, we always test a series, rather than a single patch. You can see the
> exact same report
> on any patch in a series. (it's convenient, you don't need backward to search
> the header of the series, then check result)

Convenience is subject to interpretation :-).
Other CI systems send a single report which is more sane for me.


>
> " One thing that comes to mind, do we have dpdk headers installed system-
> > wide on the Intel CI server(s)?"
>
> Sure, we do. We don't see any problem on other patch compilation, so far. but
> it's strange
> that your V2 and V3 is same, but v3 test is failed. (code base is same). So I
> will try to re-run
> your series(v3), and check what's changed on CI system between the 2 days. Is
> that helpful?

Just to be sure.
By this, you mean that you have some dpdk headers installed on the CI
system in /usr?

Having those headers most likely exacerbates races with dpdk headers
copy in the building directory.
This could be where my series failed.


####################################################################
####################################################################
From Thomas Monjalon

> On Fri, Jun 26, 2020 at 5:03 AM Chen, Zhaoyan <zhaoyan.chen@intel.com> wrote:
> >
> > Hi, David,
> >
> > For your question, "Is it normal to see all patches with the exact same
> test report?"
> > Yes, we always test a series, rather than a single patch. You can see the
> exact same report
> > on any patch in a series. (it's convenient, you don't need backward to
> search
> > the header of the series, then check result)
>
> Convenience is subject to interpretation :-).
> Other CI systems send a single report which is more sane for me.

I think these tests have 2 purposes:
        - sending quick error feedback to the author
        - check that all is green before merging
In both cases we don't need to have the same report duplicated,
because we check for failures in all patches anyway.

I suggest sending the series report only on the last patch of the series.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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=bug-493-149@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=ci@dpdk.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

DPDK CI discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/ public-inbox