Bug 112033 - Store the runner and kernel logs as part of the IGT results
Summary: Store the runner and kernel logs as part of the IGT results
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: IGT (show other bugs)
Version: XOrg git
Hardware: Other All
: not set not set
Assignee: Petri Latvala
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-16 12:28 UTC by Martin Peres
Modified: 2019-11-12 07:41 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2019-10-16 12:28:06 UTC
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?
Comment 1 Martin Peres 2019-10-16 12:29:43 UTC
The rationale behind this request is to fix the lack of dmesg for resume runs' after the machine reboots.

By fixing this in the runner, we end up fixing the issue for everyone (individual developers, Intel CI, other CIs) which lead to less duplication of efforts.
Comment 2 Martin Peres 2019-11-12 07:41:58 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/34.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.