From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 220] Add hardware usage status to the dashboard
Date: Mon, 04 Mar 2019 19:44:16 +0000 [thread overview]
Message-ID: <bug-220-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=220
Bug ID: 220
Summary: Add hardware usage status to the dashboard
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: enhancement
Priority: Normal
Component: dashboard
Assignee: ci@dpdk.org
Reporter: jplsek@iol.unh.edu
CC: jplsek@iol.unh.edu
Target Milestone: ---
Related to #144 and #147.
Since we will be adding more test cases to run, that means that more jobs could
be queued and waiting than before. Tests are also run serially to avoid
affecting performance and to run on one specific nic at a time, which again
adds time to testing.
This page would show what is the current job running on each machine and show
what jobs are queued. This will pretty much just utilize the Jenkins API.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-03-04 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 19:44 bugzilla [this message]
2019-06-17 15:44 ` 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-220-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).