From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1068534278==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id CD81C6E957 for ; Wed, 16 Oct 2019 12:28:06 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1068534278== Content-Type: multipart/alternative; boundary="15712288861.3fA2c27C3.2753" Content-Transfer-Encoding: 7bit --15712288861.3fA2c27C3.2753 Date: Wed, 16 Oct 2019 12:28:06 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D112033 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 hair= ier 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.js= on, then log the current run ID in the journal. Petri, any thoughts? --=20 You are receiving this mail because: You are the assignee for the bug.= --15712288861.3fA2c27C3.2753 Date: Wed, 16 Oct 2019 12:28:06 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
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.js=
on,
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.
= --15712288861.3fA2c27C3.2753-- --===============1068534278== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1068534278==--