From: Karolina Stolarek <karolina.stolarek@intel.com>
To: <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] ✗ GitLab.Pipeline: warning for Use intel_cmds_info in i915_pm_rpm (rev3)
Date: Thu, 29 Jun 2023 08:36:40 +0200 [thread overview]
Message-ID: <7ac8775a-9cfe-f55b-2937-2f77956cd64e@intel.com> (raw)
In-Reply-To: <168794047658.32035.495339482977027437@emeril.freedesktop.org>
On 28.06.2023 10:21, Patchwork wrote:
> == Series Details ==
>
> Series: Use intel_cmds_info in i915_pm_rpm (rev3)
> URL : https://patchwork.freedesktop.org/series/118102/
> State : warning
>
> == Summary ==
>
> Pipeline status: FAILED.
>
> see https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/920880 for the overview.
>
> containers:igt has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/44567807):
> Downloading artifacts from coordinator... ok host=gitlab.freedesktop.org id=44567792 responseStatus=200 OK token=64_SMiPp
> section_end:1687940177:download_artifacts
> section_start:1687940177:step_script
> Executing "step_script" stage of the job script
> Using docker image sha256:594aa868d31ee3304dee8cae8a3433c89a6fcfcf6c7d420c04cce22f60147176 for registry.freedesktop.org/wayland/ci-templates/buildah:2019-08-13.0 with digest registry.freedesktop.org/wayland/ci-templates/buildah@sha256:7dbcf22cd2c1c7d49db0dc7b4ab207c3d6a4a09bd81cc3b71a688d3727d8749f ...
> $ /host/bin/curl -s -L --cacert /host/ca-certificates.crt --retry 4 -f --retry-delay 60 https://gitlab.freedesktop.org/freedesktop/helm-gitlab-infra/-/raw/main/runner-gating/runner-gating.sh | sh
> Checking if the user of the pipeline is allowed...
> Checking if the job's project is part of a well-known group...
> Thank you for contributing to freedesktop.org
> $ podman login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
> Login Succeeded!
> $ .gitlab-ci/pull-or-rebuild.sh igt Dockerfile igt
> STEP 1: FROM registry.freedesktop.org/gfx-ci/igt-ci-tags/build-fedora:commit-c7285ff813a8c1caff55691f39366eaf9589821f
> Error: error creating build container: Error initializing source docker://registry.freedesktop.org/gfx-ci/igt-ci-tags/build-fedora:commit-c7285ff813a8c1caff55691f39366eaf9589821f: Error reading manifest commit-c7285ff813a8c1caff55691f39366eaf9589821f in registry.freedesktop.org/gfx-ci/igt-ci-tags/build-fedora: received unexpected HTTP status: 500 Internal Server Error
> section_end:1687940179:step_script
> section_start:1687940179:cleanup_file_variables
> Cleaning up project directory and file based variables
> section_end:1687940179:cleanup_file_variables
> ERROR: Job failed: exit code 1
Looks like a CI hiccup. All the tests have passed and BAT/IGT were run
with no significant issues.
Thanks,
Karolina
> == Logs ==
>
> For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/920880
next prev parent reply other threads:[~2023-06-29 6:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 10:58 [igt-dev] [PATCH i-g-t v2 0/3] Use intel_cmds_info in i915_pm_rpm Karolina Stolarek
2023-06-27 10:58 ` [igt-dev] [PATCH i-g-t v2 1/3] lib/intel_cmds_info: Add library support for XY_COLOR_BLT Karolina Stolarek
2023-06-30 15:40 ` Kamil Konieczny
2023-06-27 10:58 ` [igt-dev] [PATCH i-g-t v2 2/3] tests/i915/i915_pm_rpm: Modify gem-execbuf test for gen12+ Karolina Stolarek
2023-06-30 15:41 ` Kamil Konieczny
2023-06-27 10:58 ` [igt-dev] [PATCH i-g-t v2 3/3] tests/i915/i915_pm_rpm: Check command property instead of gen Karolina Stolarek
2023-06-30 15:42 ` Kamil Konieczny
2023-06-28 8:21 ` [igt-dev] ✗ GitLab.Pipeline: warning for Use intel_cmds_info in i915_pm_rpm (rev3) Patchwork
2023-06-29 6:36 ` Karolina Stolarek [this message]
2023-06-28 8:50 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-06-28 21:45 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-06-29 6:34 ` Karolina Stolarek
2023-06-30 7:35 ` Yedireswarapu, SaiX Nandan
2023-06-30 7:29 ` [igt-dev] ✓ Fi.CI.IGT: success " 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=7ac8775a-9cfe-f55b-2937-2f77956cd64e@intel.com \
--to=karolina.stolarek@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