From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
Arunpravin Paneer Selvam <arunpravin.paneerselvam@amd.com>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for tests/drm_buddy: Add drm buddy test cases
Date: Mon, 11 Apr 2022 15:28:31 +0000 [thread overview]
Message-ID: <9e71bc51f1534086a9a56dca42c02c65@intel.com> (raw)
In-Reply-To: <CAM0jSHOiGExPcGnY9kOK6vf4Dd8dd65o3BmynHdhY8HiwQZsFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5426 bytes --]
Shards run will trigger automatically.
From: Matthew Auld <matthew.william.auld@gmail.com>
Sent: Monday, April 11, 2022 7:56 AM
To: Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Cc: igt-dev@lists.freedesktop.org; Arunpravin Paneer Selvam <arunpravin.paneerselvam@amd.com>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for tests/drm_buddy: Add drm buddy test cases
On Mon, 11 Apr 2022 at 15:42, Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com<mailto:lakshminarayana.vudum@intel.com>> wrote:
It’s related to https://gitlab.freedesktop.org/drm/intel/-/issues/5616
igt@runner@aborted - fail - BUG: kernel NULL pointer dereference, address: 0000000000000008, RIP: 0010:dma_resv_add_fence
Ok. I assume you can still trigger shards run? This new buddy test case should be triggered there I hope.
@Matthew Auld<mailto:matthew.william.auld@gmail.com> Btw, from which build we shouldn’t be seeing this bug https://gitlab.freedesktop.org/drm/intel/-/issues/5602 ?
It should have been CI_DRM_11476. At least according to https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11476/git-log-oneline.txt
Thanks,
Lakshmi.
From: Matthew Auld <matthew.william.auld@gmail.com<mailto:matthew.william.auld@gmail.com>>
Sent: Monday, April 11, 2022 2:39 AM
To: igt-dev@lists.freedesktop.org<mailto:igt-dev@lists.freedesktop.org>; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com<mailto:lakshminarayana.vudum@intel.com>>
Cc: Arunpravin Paneer Selvam <arunpravin.paneerselvam@amd.com<mailto:arunpravin.paneerselvam@amd.com>>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for tests/drm_buddy: Add drm buddy test cases
On Mon, 11 Apr 2022 at 09:19, Patchwork <patchwork@emeril.freedesktop.org<mailto:patchwork@emeril.freedesktop.org>> wrote:
Patch Details
Series:
tests/drm_buddy: Add drm buddy test cases
URL:
https://patchwork.freedesktop.org/series/102469/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6912/index.html
CI Bug Log - changes from CI_DRM_11481 -> IGTPW_6912
Summary
FAILURE
Serious unknown changes coming with IGTPW_6912 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_6912, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6912/index.html
Participating hosts (47 -> 44)
Additional (2): fi-pnv-d510 bat-dg1-5
Missing (5): shard-tglu fi-bsw-cyan fi-icl-u2 shard-dg1 fi-bdw-samus
Possible new issues
Here are the unknown changes that may have been introduced in IGTPW_6912:
IGT changes
Possible regressions
* igt@runner@aborted:
* bat-dg1-5: NOTRUN -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6912/bat-dg1-5/igt@runner@aborted.html>
Lakshmi, looks like unrelated failure.
*
Suppressed
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@i915_selftest@live@gt_pm:
* {fi-tgl-dsi}: DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/fi-tgl-dsi/igt@i915_selftest@live@gt_pm.html> (i915#1759<https://gitlab.freedesktop.org/drm/intel/issues/1759>) -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6912/fi-tgl-dsi/igt@i915_selftest@live@gt_pm.html>
Known issues
Here are the changes found in IGTPW_6912 that come from known issues:
IGT changes
Issues hit
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c:
* fi-pnv-d510: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6912/fi-pnv-d510/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#5341<https://gitlab.freedesktop.org/drm/intel/issues/5341>)
* igt@prime_vgem@basic-userptr:
* fi-pnv-d510: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6912/fi-pnv-d510/igt@prime_vgem@basic-userptr.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +57 similar issues
* igt@runner@aborted:
* fi-bdw-5557u: NOTRUN -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6912/fi-bdw-5557u/igt@runner@aborted.html> (i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312>)
* fi-hsw-4770: NOTRUN -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6912/fi-hsw-4770/igt@runner@aborted.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#2722<https://gitlab.freedesktop.org/drm/intel/issues/2722> / i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312> / i915#5594<https://gitlab.freedesktop.org/drm/intel/issues/5594>)
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
Build changes
* CI: CI-20190529 -> None
* IGT: IGT_6415 -> IGTPW_6912
CI-20190529: 20190529
CI_DRM_11481: 9bf68eb47288411da23ce5c9967f27dba43bda1d @ git://anongit.freedesktop.org/gfx-ci/linux<http://anongit.freedesktop.org/gfx-ci/linux>
IGTPW_6912: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6912/index.html
IGT_6415: c3b690bd5f7fb1fb7ed786ab0f3b815930a6a55f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
== Testlist changes ==
+igt@drm_buddy@all
[-- Attachment #2: Type: text/html, Size: 41710 bytes --]
next prev parent reply other threads:[~2022-04-11 15:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 7:28 [PATCH] tests/drm_buddy: Add drm buddy test cases Arunpravin Paneer Selvam
2022-04-11 7:28 ` Arunpravin Paneer Selvam
2022-04-11 7:28 ` [Intel-gfx] " Arunpravin Paneer Selvam
2022-04-11 7:28 ` [igt-dev] " Arunpravin Paneer Selvam
2022-04-11 8:14 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
2022-04-11 8:19 ` [igt-dev] ✗ Fi.CI.BAT: " Patchwork
2022-04-11 9:39 ` Matthew Auld
2022-04-11 14:42 ` Vudum, Lakshminarayana
2022-04-11 14:56 ` Matthew Auld
2022-04-11 15:28 ` Vudum, Lakshminarayana [this message]
2022-04-11 9:38 ` [PATCH] " Matthew Auld
2022-04-11 9:38 ` Matthew Auld
2022-04-11 9:38 ` [Intel-gfx] " Matthew Auld
2022-04-11 9:38 ` [igt-dev] " Matthew Auld
2022-04-11 14:57 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2022-04-11 16:48 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=9e71bc51f1534086a9a56dca42c02c65@intel.com \
--to=lakshminarayana.vudum@intel.com \
--cc=arunpravin.paneerselvam@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=matthew.william.auld@gmail.com \
/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.