From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ci-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by dpdk.space (Postfix) with ESMTP id 2EB5AA00E6
	for <public@inbox.dpdk.org>; Mon, 15 Apr 2019 19:44:38 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 033CD1B3B3;
	Mon, 15 Apr 2019 19:44:38 +0200 (CEST)
Received: by dpdk.org (Postfix, from userid 33)
 id 2C7D91B3B3; Mon, 15 Apr 2019 19:44:37 +0200 (CEST)
From: bugzilla@dpdk.org
To: ci@dpdk.org
Date: Mon, 15 Apr 2019 17:44:37 +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: <bug-254-149@http.bugs.dpdk.org/>
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 254] Auto create measurements and test cases as
 results are submitted
X-BeenThere: ci@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK CI discussions <ci.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/ci>,
 <mailto:ci-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/ci/>
List-Post: <mailto:ci@dpdk.org>
List-Help: <mailto:ci-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/ci>,
 <mailto:ci-request@dpdk.org?subject=subscribe>
Errors-To: ci-bounces@dpdk.org
Sender: "ci" <ci-bounces@dpdk.org>

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

            Bug ID: 254
           Summary: Auto create measurements and test cases as results are
                    submitted
           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: ---

Currently, measurements for results must be put in by hand from the admin
interface/rest api. So for example, currently, if a test run wants to add a=
 new
measurement, they have to create the measurements before sending the test
results.

Instead, make it so that if a measurement does not exist when a test result=
 is
submitted, just create the new measurement dynamically. This allows freely
changing measurements without the user needing to explicitly create the
measurement.

Part of the reason this was done was for the database to automatically know
what test case the result was meant for without needing it to be specified =
in
the results JSON.

This would require updating the JSON results to also specify the test case =
the
test run/measurements was meant for.

At the same time, the test case could also be automatically created. However
the description/url of the test case would probably have to be added in aft=
er
the fact.

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