Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: vitaly.prosyak@amd.com
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✓ CI.xeBAT: success for series starting with [1/2] tests/amdgpu: split deadlock tests
Date: Sat, 23 Sep 2023 01:20:18 -0000	[thread overview]
Message-ID: <169543201864.3504.407561564211043617@emeril.freedesktop.org> (raw)
In-Reply-To: <20230922234204.9782-1-vitaly.prosyak@amd.com>

[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]

== Series Details ==

Series: series starting with [1/2] tests/amdgpu: split deadlock tests
URL   : https://patchwork.freedesktop.org/series/124150/
State : success

== Summary ==

CI Bug Log - changes from XEIGT_7499_BAT -> XEIGTPW_9859_BAT
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  

Participating hosts (4 -> 4)
------------------------------

  No changes in participating hosts

Known issues
------------

  Here are the changes found in XEIGTPW_9859_BAT that come from known issues:

### IGT changes ###

#### Possible fixes ####

  * {igt@xe_create@create-execqueues-noleak}:
    - bat-atsm-2:         [FAIL][1] ([Intel XE#524]) -> [PASS][2]
   [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_7499/bat-atsm-2/igt@xe_create@create-execqueues-noleak.html
   [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_9859/bat-atsm-2/igt@xe_create@create-execqueues-noleak.html

  
  {name}: This element is suppressed. This means it is ignored when computing
          the status of the difference (SUCCESS, WARNING, or FAILURE).

  [Intel XE#524]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/524


Build changes
-------------

  * IGT: IGT_7499 -> IGTPW_9859
  * Linux: xe-390-6149acb947f2f8b65ee1a058982a5d6fce3124ec -> xe-392-16e2c940ef53f81b2c68e16ec39cf5772894a625

  IGTPW_9859: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9859/index.html
  IGT_7499: d991240f6c6751e9480456c20de785cfc6e6ff15 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
  xe-390-6149acb947f2f8b65ee1a058982a5d6fce3124ec: 6149acb947f2f8b65ee1a058982a5d6fce3124ec
  xe-392-16e2c940ef53f81b2c68e16ec39cf5772894a625: 16e2c940ef53f81b2c68e16ec39cf5772894a625

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_9859/index.html

[-- Attachment #2: Type: text/html, Size: 2406 bytes --]

  parent reply	other threads:[~2023-09-23  1:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22 23:42 [igt-dev] [PATCH 1/2] tests/amdgpu: split deadlock tests vitaly.prosyak
2023-09-22 23:42 ` [igt-dev] [PATCH 2/2] tests/amdgpu: add GFX11 to dispatch tests vitaly.prosyak
2023-09-23  0:05 ` [igt-dev] ✗ GitLab.Pipeline: warning for series starting with [1/2] tests/amdgpu: split deadlock tests Patchwork
2023-09-23  0:38 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-09-23  1:20 ` Patchwork [this message]
2023-09-24  4:49 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-09-26  0:51 [igt-dev] [PATCH 1/2] " vitaly.prosyak
2023-09-26  1:40 ` [igt-dev] ✓ CI.xeBAT: success for series starting with [1/2] " 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=169543201864.3504.407561564211043617@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=vitaly.prosyak@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox