Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ GitLab.Pipeline: warning for Build Xe test documentation (rev2)
Date: Tue, 21 Mar 2023 10:34:14 -0000	[thread overview]
Message-ID: <167939485442.18676.9903553674396557560@emeril.freedesktop.org> (raw)
In-Reply-To: <20230321092205.1640976-1-mauro.chehab@linux.intel.com>

== Series Details ==

Series: Build Xe test documentation (rev2)
URL   : https://patchwork.freedesktop.org/series/115373/
State : warning

== Summary ==

Pipeline status: FAILED.

see https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/834746 for the overview.

build:tests-debian-meson-armhf has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/38460573):
  $ /host/bin/curl --cacert /host/ca-certificates.crt -s -L --retry 4 -f --retry-delay 60 https://gitlab.freedesktop.org/freedesktop/helm-gitlab-infra/-/raw/main/runner-gating/runner-gating.sh | sh -s -- pre_get_sources_script
  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
  Fetching changes...
  Reinitialized existing Git repository in /builds/gfx-ci/igt-ci-tags/.git/
  Checking out b7f294da as detached HEAD (ref is intel/IGTPW_8651)...
  Removing build/
  Removing lib/i915/perf-configs/__pycache__/
  
  Skipping Git submodules setup
  section_end:1679394241:get_sources
  section_start:1679394241:step_script
  Executing "step_script" stage of the job script
  Using docker image sha256:4a4103f1a476d355d866b481ff96ac05a32a3a715cefcc1cbc1356a8959fb5f8 for registry.freedesktop.org/gfx-ci/igt-ci-tags/build-debian-armhf:commit-b7f294da185926095640251037ca335460891f46 with digest registry.freedesktop.org/gfx-ci/igt-ci-tags/build-debian-armhf@sha256:3a0ffeb305cdc6ef081dde81d86afee76102e74f76c0f7bd5685fc2457ec707b ...
  section_end:1679394242:step_script
  section_start:1679394242:cleanup_file_variables
  Cleaning up project directory and file based variables
  section_end:1679394243:cleanup_file_variables
  ERROR: Job failed (system failure): Error response from daemon: container 82a6ca174992ce1b49f3d40074619cd3190d42c7d2b43e019c11fb7349e0ff8a does not exist in database: no such container (exec.go:78:0s)

build:tests-debian-minimal has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/38460572):
  Configuring defs.rst using configuration
  Program rst2man-3 found: NO
  Program rst2man found: NO
  Program rst2man.sh found: YES (/builds/gfx-ci/igt-ci-tags/man/rst2man.sh)
  Program igt_doc.py found: YES (/builds/gfx-ci/igt-ci-tags/scripts/igt_doc.py)
  Program gen_rst_index found: YES (/builds/gfx-ci/igt-ci-tags/scripts/gen_rst_index)
  Program sphinx-build found: NO
  Program rst2html-3 found: NO
  Program rst2html found: NO
  Program rst2pdf found: NO
  
  docs/testplan/meson.build:9:0: ERROR:  Unknown variable "xe_test_config".
  
  A full log can be found at /builds/gfx-ci/igt-ci-tags/build/meson-logs/meson-log.txt
  section_end:1679394225:step_script
  section_start:1679394225:cleanup_file_variables
  Cleaning up project directory and file based variables
  section_end:1679394225:cleanup_file_variables
  ERROR: Job failed: exit code 1
  

build:tests-fedora has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/38460566):
  Installing /builds/gfx-ci/igt-ci-tags/tests/intel-ci/README to /builds/gfx-ci/igt-ci-tags/installdir/opt/igt/share/igt-gpu-tools
  Installing /builds/gfx-ci/igt-ci-tags/tests/intel-ci/blacklist.txt to /builds/gfx-ci/igt-ci-tags/installdir/opt/igt/share/igt-gpu-tools
  Installing /builds/gfx-ci/igt-ci-tags/tests/intel-ci/blacklist-pre-merge.txt to /builds/gfx-ci/igt-ci-tags/installdir/opt/igt/share/igt-gpu-tools
  Installing /builds/gfx-ci/igt-ci-tags/tests/intel-ci/xe-fast-feedback.testlist to /builds/gfx-ci/igt-ci-tags/installdir/opt/igt/share/igt-gpu-tools
  Installing /builds/gfx-ci/igt-ci-tags/tools/intel_gpu_abrt to /builds/gfx-ci/igt-ci-tags/installdir/opt/igt/bin
  Installing /builds/gfx-ci/igt-ci-tags/build/assembler/intel-gen4asm.pc to /builds/gfx-ci/igt-ci-tags/installdir/opt/igt/lib64/pkgconfig
  Installing /builds/gfx-ci/igt-ci-tags/scripts/code_cov_capture to /builds/gfx-ci/igt-ci-tags/installdir/opt/igt/bin
  Installing /builds/gfx-ci/igt-ci-tags/scripts/code_cov_gather_on_build to /builds/gfx-ci/igt-ci-tags/installdir/opt/igt/bin
  Installing /builds/gfx-ci/igt-ci-tags/scripts/code_cov_gather_on_test to /builds/gfx-ci/igt-ci-tags/installdir/opt/igt/bin
  Installing /builds/gfx-ci/igt-ci-tags/scripts/code_cov_gen_report to /builds/gfx-ci/igt-ci-tags/installdir/opt/igt/bin
  Installing /builds/gfx-ci/igt-ci-tags/scripts/code_cov_parse_info to /builds/gfx-ci/igt-ci-tags/installdir/opt/igt/bin
  $ ninja -C build -j${FDO_CI_CONCURRENT:-4} igt-gpu-tools-doc
  ninja: Entering directory `build'
  ninja: error: unknown target 'igt-gpu-tools-doc'
  section_end:1679394335:step_script
  section_start:1679394335:cleanup_file_variables
  Cleaning up project directory and file based variables
  section_end:1679394337:cleanup_file_variables
  ERROR: Job failed: exit code 1
  

build:tests-fedora-oldest-meson has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/38460568):
  [1332/1342] Compiling C object 'lib/lib@@i915_perf@sha/meson-generated_.._i915_perf_registers_acmgt3.c.o'.
  [1333/1342] Linking target lib/libi915_perf.so.1.5.
  [1334/1342] Generating symbol file 'lib/lib@@i915_perf@sha/libi915_perf.so.1.5.symbols'.
  [1335/1342] Linking target tools/i915-perf/i915-perf-configs.
  [1336/1342] Linking target tools/i915-perf/i915-perf-recorder.
  [1337/1342] Linking target tests/core_hotunplug.
  [1338/1342] Linking target tools/i915-perf/i915-perf-reader.
  [1339/1342] Linking target tests/perf.
  [1340/1342] Linking target tests/gem_barrier_race.
  [1341/1342] Generating xe_tests.rst with a custom command.
  [1342/1342] Generating xe_tests.html with a custom command.
  $ ninja -C build -j${FDO_CI_CONCURRENT:-4} igt-gpu-tools-doc
  ninja: Entering directory `build'
  ninja: error: unknown target 'igt-gpu-tools-doc'
  section_end:1679394338:step_script
  section_start:1679394338:cleanup_file_variables
  Cleaning up project directory and file based variables
  section_end:1679394339:cleanup_file_variables
  ERROR: Job failed: exit code 1

== Logs ==

For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/834746


  parent reply	other threads:[~2023-03-21 10:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21  9:22 [igt-dev] [PATCH i-g-t v3 0/4] Build Xe test documentation Mauro Carvalho Chehab
2023-03-21  9:22 ` [igt-dev] [PATCH i-g-t v3 1/4] meson: build " Mauro Carvalho Chehab
2023-03-21  9:22 ` [igt-dev] [PATCH i-g-t v3 2/4] testplan: build also a PDF file with the testplan Mauro Carvalho Chehab
2023-03-21  9:22 ` [igt-dev] [PATCH i-g-t v3 3/4] meson.build: place gtk-doc dependencies check at the right place Mauro Carvalho Chehab
2023-03-21  9:22 ` [igt-dev] [PATCH i-g-t v3 4/4] testplan/meson.build: cleanup dependency chain Mauro Carvalho Chehab
2023-03-21 10:34 ` Patchwork [this message]
2023-03-21 10:56 ` [igt-dev] ✗ Fi.CI.BAT: failure for Build Xe test documentation (rev2) 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=167939485442.18676.9903553674396557560@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=mauro.chehab@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox