Pre-Merge Results

A handy overview of the emails with results sent by i915 CI.

The Sections

Test Results

See Understanding The Test Results for details on how to read failures/fixes.

Participating Hosts

This sections how many hosts participated in the run and the delta in comparison to the base run.

Small fluctuations are expected, as we deal with rebooting and AC-cutting physical machines - some of the host require manual intervention from time to time or may take longer than expected to boot due to automated fscks.

When assessing impact of series look for large deltas and/or patterns (e.g. half of the machines missing, or all GEN8 machines missing).

Participating hosts (52 -> 47)

  Additional (2): fi-byt-j1900 fi-bsw-kefka
  Missing    (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus 

Build Changes

This section lists the delta in components deployed on the machines doing the testing.

You should see only one component change at a time (e.g. post-merge kernel changed to the pre-merge) unless you are testing combined IGT and kernel changes.

Prefix Explanation
CI_DRM_ post-merge of drm-tip serving as a baseline for comparison
Patchwork_ pre-merge of drm-tip with patches applied
Trybot_ pre-merge of drm-tip with patches applied (trybot)
IGT_ post-merge of IGT serving as a baseline for comparison
IGTPW_ pre-merge of IGT with patches applied
TrybotIGT_ pre-merge of drm-tip with patches applied (trybot)
Build changes

  * Linux: CI_DRM_6039 -> Patchwork_12960

  CI_DRM_6039: 941848427de77537b5709bd68ca4a4048be5b5d9 @ git://
  IGT_4972: f052e49a43cc9704ea5f240df15dd9d3dfed68ab @ git://
  Patchwork_12960: 824b9e2304e344e55b1fea49f624c7b2ab0725bf @ git://

See Reproducing The Tree on details how to read the SHA1/repos.

Understanding The Test Results

* igt@i915_suspend@debugfs-reader:
 - shard-apl:          [PASS][5] -> [DMESG-WARN][6] ([fdo#108566]) +3 similar issues


Each test state change (e.g. pass→fail) has few things listed:

I’ve Got Some False Positives, What Now?

Reply to the e-mail with the results and explain why do those results are false positive in as much detail as you can.

Include the following people in the CC:

Reproducing The Tree

The easiest way is using “build changes” section.

Build changes

    * Linux: CI_DRM_5951 -> Patchwork_12825

  CI_DRM_5951: 08cf1213114f21fc0b1a17eac081a2db8c03311f @ git://
  IGT_4956: 1d921615b0b706f25c856aa0eb096f274380c199 @ git://
  Patchwork_12825: f3e8eb0c781a6a88cd6f67a64f4b93e132cb37fe @ git://
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://

Each component here has three things mentioned: it’s name (which is also a tag), SHA1 and git remote where given SHA1 and/or tag can be found.

$ git remote -v
ci-tags git:// (fetch)
ci-tags git:// (push)

$ git fetch --tags ci-tags

$ git tag | grep Patchwork_12825

$ git checkout intel/Patchwork_12825
Note: checking out 'intel/Patchwork_12825'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f3e8eb0c781a drm/i915: Add transcoder parameter to PSR registers macros

For the Kernel, if you want to check which upstream relase the tree is based on you can fetch Linus’ tags and use git describe to find the parent annotated tag (CI tags are not annotaded).

$ git remote add linus git://

$ git fetch --tags linus

$ git describe intel/Patchwork_12825

NOTE: IGT pre-merge tagging is still WIP. For now use SHA1 on the main repository. In the meantime checkout the IGT repository to SHA1 mentioned by the IGT_ component and apply the mbox downloaded from the patchwork.