DPDK CI discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 411] Intel performance testing currently down
Date: Wed, 26 Feb 2020 16:48:40 +0000	[thread overview]
Message-ID: <bug-411-149@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 411
           Summary: Intel performance testing currently down
           Product: lab
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: UNH infra
          Assignee: ci@dpdk.org
          Reporter: jplsek@iol.unh.edu
                CC: jplsek@iol.unh.edu
  Target Milestone: ---

There were concerns about inconsistent results.

See: http://mails.dpdk.org/archives/ci/2020-February/000505.html

Currently we are trying to get DTS updated to see if this will resolve the
issue. The latest DTS is crashing on the systems and we are waiting on feedback
for how to resolve this issue or for the vendor fix it on their system.

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

             reply	other threads:[~2020-02-26 16:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 16:48 bugzilla [this message]
2020-04-07 13:22 ` 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-411-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
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).