DPDK CI discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 431] Missing performance results in Patchwork checks, and possible false positives
Date: Tue, 31 Mar 2020 14:42:51 +0000
Message-ID: <bug-431-149@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 431
           Summary: Missing performance results in Patchwork checks, and
                    possible false positives
           Product: lab
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: job scripts
          Assignee: ci@dpdk.org
          Reporter: alialnu@mellanox.com
                CC: dpdklab@iol.unh.edu
  Target Milestone: ---

Sometimes, not all of the performance results for a vendor are sent in the same
email to the mailing list. For example, for patch 67243
(http://dpdk.org/patch/67243), I see 2 reports:

1. http://mails.dpdk.org/archives/test-report/2020-March/122345.html (Mellanox
ConnectX-5 100000 Mbps & Mellanox ConnectX-4 Lx 25000 Mbps).
2. http://mails.dpdk.org/archives/test-report/2020-March/122348.html (Mellanox
ConnectX-4 Lx 40000 Mbps).

This might be a problem because only the last check will appear in Patchwork.
Is this an expected behavior?
Would a second report with "success" status be sent after a report with
"failure" status? Because this would cause the Patchwork check to be a false
positive.

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

             reply	other threads:[~2020-03-31 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 14:42 bugzilla [this message]
2020-04-19 13:31 ` Ali Alnubani
2020-04-22 16:34 ` bugzilla

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=bug-431-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

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://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/ https://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


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