From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 112033] Store the runner and kernel logs as part of the IGT results
Date: Wed, 16 Oct 2019 12:28:06 +0000 [thread overview]
Message-ID: <bug-112033-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1263 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=112033
Bug ID: 112033
Summary: Store the runner and kernel logs as part of the IGT
results
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: not set
Priority: not set
Component: IGT
Assignee: dri-devel@lists.freedesktop.org
Reporter: martin.peres@free.fr
While it might appear like a trivial request to some, this is a little hairier
than what it might initially appear.
The main issue comes from the fact that runs can be resumed, so it means we
need to distinguish every execution and be able to say which subtest got
executed on which run (CI Bug Log's testsuiterun 's run ID).
This is made a little harder by the fact that a binary execution can execute
multiple tests and we need to support resuming it while still being able to say
which subtest were executed on which run.
So far, the idea is to store the current run ID in the runner's metadata.json,
then log the current run ID in the journal.
Petri, any thoughts?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2549 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-10-16 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 12:28 bugzilla-daemon [this message]
2019-10-16 12:29 ` [Bug 112033] Store the runner and kernel logs as part of the IGT results bugzilla-daemon
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-112033-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.