From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ GitLab.Pipeline: warning for D3Cold Tool & IGT
Date: Fri, 22 Apr 2022 05:35:49 -0400 [thread overview]
Message-ID: <YmJ29T3cMpyawmfh@intel.com> (raw)
In-Reply-To: <165028686531.11405.10073846949189988435@emeril.freedesktop.org>
On Mon, Apr 18, 2022 at 01:01:05PM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: D3Cold Tool & IGT
> URL : https://patchwork.freedesktop.org/series/102780/
> State : warning
>
> == Summary ==
>
> Pipeline status: FAILED.
>
> see https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/562529 for the overview.
>
> test:ninja-test-armhf has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/21360839):
> Ok: 22
> Expected Fail: 3
> Fail: 289
This is awful, but I couldn't find any current library change in this series
that would justify this amount of fail.
I already glanced through all the patches in this series and will continue
with the review in a hope that I find what is causing this.
I notice that igt_assert_f is used in patch 3, but not modified...
> Unexpected Pass: 0
> Skipped: 0
> Timeout: 0
>
> Full log written to /builds/gfx-ci/igt-ci-tags/build/meson-logs/testlog.txt
> section_end:1650286681:step_script
> section_start:1650286681:upload_artifacts_on_failure
> Uploading artifacts for failed job
> Uploading artifacts...
> build: found 1728 matching files and directories
> Uploading artifacts as "archive" to coordinator... 201 Created id=21360839 responseStatus=201 Created token=iQxHfmmd
> section_end:1650286689:upload_artifacts_on_failure
> section_start:1650286689:cleanup_file_variables
> Cleaning up project directory and file based variables
> section_end:1650286690:cleanup_file_variables
> ERROR: Job failed: exit code 1
>
> == Logs ==
>
> For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/562529
next prev parent reply other threads:[~2022-04-22 9:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 12:50 [igt-dev] [PATCH i-g-t 0/9] D3Cold Tool & IGT Anshuman Gupta
2022-04-18 12:50 ` [igt-dev] [PATCH i-g-t 1/9] test/i915_pm_rpm: Add placement to gem-{mmap-type, execbuf} Anshuman Gupta
2022-04-22 9:26 ` Rodrigo Vivi
2022-04-18 12:50 ` [igt-dev] [PATCH i-g-t 2/9] lib/igt_device: Get gfx PCI card root port Anshuman Gupta
2022-04-22 9:29 ` Rodrigo Vivi
2022-04-18 12:50 ` [igt-dev] [PATCH i-g-t 3/9] lib/igt_pm: D3Cold runtime pm infrastructure Anshuman Gupta
2022-04-22 10:16 ` Rodrigo Vivi
2022-04-26 12:23 ` Gupta, Anshuman
2022-04-26 13:22 ` Rodrigo Vivi
2022-04-26 16:06 ` Kamil Konieczny
2022-04-18 12:50 ` [igt-dev] [PATCH i-g-t 4/9] lib/intel_device_info: Add IS_DGFX() support Anshuman Gupta
2022-04-22 10:17 ` Rodrigo Vivi
2022-04-18 12:50 ` [igt-dev] [PATCH i-g-t 5/9] tools: Add intel_pm_rpm tool Anshuman Gupta
2022-04-22 10:22 ` Rodrigo Vivi
2022-04-22 12:07 ` Rodrigo Vivi
2022-04-28 6:59 ` Gupta, Anshuman
2022-04-28 8:38 ` Vivi, Rodrigo
2022-04-29 8:58 ` Gupta, Anshuman
2022-04-22 12:08 ` Gupta, Anshuman
2022-04-18 12:50 ` [igt-dev] [PATCH i-g-t 6/9] i915_pm_rpm: Add D3Cold basic subtest Anshuman Gupta
2022-04-22 12:01 ` Rodrigo Vivi
2022-04-22 14:22 ` Kamil Konieczny
2022-04-18 12:50 ` [igt-dev] [PATCH i-g-t 7/9] i915_pm_rpm: Test D3Cold with gem_exec_stress Anshuman Gupta
2022-04-22 12:03 ` Rodrigo Vivi
2022-04-18 12:50 ` [igt-dev] [PATCH i-g-t 8/9] i915_pm_rpm: Extend gem_execbuf test with D3Cold Anshuman Gupta
2022-04-22 12:04 ` Rodrigo Vivi
2022-04-18 12:50 ` [igt-dev] [PATCH i-g-t 9/9] i915_pm_rpm: Extend gem-mmap-type " Anshuman Gupta
2022-04-22 12:05 ` Rodrigo Vivi
2022-04-18 13:01 ` [igt-dev] ✗ GitLab.Pipeline: warning for D3Cold Tool & IGT Patchwork
2022-04-22 9:35 ` Rodrigo Vivi [this message]
2022-04-22 11:19 ` Petri Latvala
2022-04-18 13:34 ` [igt-dev] ✗ Fi.CI.BAT: 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=YmJ29T3cMpyawmfh@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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