From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Swati Sharma" <swati2.sharma@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BUILD: failure for tests/i915/kms_flip_scaled_crc: New tests (rev10)
Date: Tue, 28 Jun 2022 20:04:38 -0000 [thread overview]
Message-ID: <165644667856.14502.10280855083824732712@emeril.freedesktop.org> (raw)
In-Reply-To: <20220628185128.19692-1-swati2.sharma@intel.com>
== Series Details ==
Series: tests/i915/kms_flip_scaled_crc: New tests (rev10)
URL : https://patchwork.freedesktop.org/series/105148/
State : failure
== Summary ==
IGT patchset build failed on latest successful build
9b9371c8da32533022ad700a7c023b4c3a085fbc tests/i915: adapt __copy_ccs for discrete
297/329 testcase check amdgpu/amd_basic OK 0.18s
298/329 testcase check amdgpu/amd_bypass OK 0.17s
299/329 testcase check amdgpu/amd_cs_nop OK 0.17s
300/329 testcase check amdgpu/amd_hotplug OK 0.16s
301/329 testcase check amdgpu/amd_color OK 0.17s
302/329 testcase check amdgpu/amd_info OK 0.15s
303/329 testcase check amdgpu/amd_prime OK 0.15s
304/329 testcase check amdgpu/amd_max_bpc OK 0.14s
305/329 testcase check amdgpu/amd_module_load OK 0.14s
306/329 testcase check amdgpu/amd_mem_leak OK 0.13s
307/329 testcase check amdgpu/amd_link_settings OK 0.13s
308/329 testcase check amdgpu/amd_vrr_range OK 0.13s
309/329 testcase check amdgpu/amd_mode_switch OK 0.12s
310/329 testcase check amdgpu/amd_dp_dsc OK 0.11s
311/329 testcase check amdgpu/amd_psr OK 0.11s
312/329 testcase check amdgpu/amd_plane OK 0.11s
313/329 testcase check amdgpu/amd_ilr OK 0.10s
314/329 runner_json OK 0.08s
315/329 assembler test/mov OK 0.08s
316/329 assembler test/frc OK 0.07s
317/329 assembler test/regtype OK 0.07s
318/329 assembler test/rndd OK 0.07s
319/329 assembler test/rndu OK 0.05s
320/329 assembler test/rnde OK 0.05s
321/329 assembler test/rnde-intsrc OK 0.05s
322/329 assembler test/rndz OK 0.04s
323/329 assembler test/lzd OK 0.04s
324/329 assembler test/not OK 0.04s
325/329 assembler test/immediate OK 0.03s
326/329 lib igt_nesting OK 2.21s
327/329 lib igt_fork OK 2.64s
328/329 runner OK 4.73s
329/329 testcase check gem_concurrent_all OK 5.51s
Summary of Failures:
282/329 testcase check kms_flip_scaled_crc FAIL 0.38s exit status 1
Ok: 325
Expected Fail: 3
Fail: 1
Unexpected Pass: 0
Skipped: 0
Timeout: 0
Full log written to /home/cidrm/igt-gpu-tools/build/meson-logs/testlog.txt
FAILED: meson-test
/usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
prev parent reply other threads:[~2022-06-28 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 18:51 [igt-dev] [v6 PATCH i-g-t 0/4] tests/i915/kms_flip_scaled_crc: New tests Swati Sharma
2022-06-28 18:51 ` [igt-dev] [v5 PATCH i-g-t 1/4] tests/i915/kms_flip_scaled_crc: Convert tests to dynamic Swati Sharma
2022-06-28 18:51 ` [igt-dev] [v2 PATCH i-g-t 2/4] tests/i915/kms_flip_scaled_crc: Add new tests covering modifiers and pixel-formats Swati Sharma
2022-06-28 18:51 ` [igt-dev] [v2 PATCH i-g-t 3/4] lib/igt_kms: Add scaling filter property Swati Sharma
2022-06-29 12:36 ` Juha-Pekka Heikkila
2022-06-28 18:51 ` [igt-dev] [v5 PATCH i-g-t 4/4] tests/kms_flip_scaled_crc: Validate NN scaling filter Swati Sharma
2022-06-29 12:37 ` Juha-Pekka Heikkila
2022-06-28 20:04 ` Patchwork [this message]
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=165644667856.14502.10280855083824732712@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=swati2.sharma@intel.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.