From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 33) id 59DCC4C8E; Mon, 4 Mar 2019 20:44:16 +0100 (CET) From: bugzilla@dpdk.org To: ci@dpdk.org Date: Mon, 04 Mar 2019 19:44:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: lab X-Bugzilla-Component: dashboard X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jplsek@iol.unh.edu X-Bugzilla-Status: CONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: ci@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-ci] [Bug 220] Add hardware usage status to the dashboard X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Mar 2019 19:44:16 -0000 https://bugs.dpdk.org/show_bug.cgi?id=3D220 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 c= ould 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 sh= ow what jobs are queued. This will pretty much just utilize the Jenkins API. --=20 You are receiving this mail because: You are the assignee for the bug.=