DPDK CI discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 254] Auto create measurements and test cases as results are submitted
Date: Mon, 15 Apr 2019 17:44:37 +0000	[thread overview]
Message-ID: <bug-254-149@http.bugs.dpdk.org/> (raw)

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

            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 after
the fact.

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

                 reply	other threads:[~2019-04-15 17:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-254-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).