All of 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 (rev3)
Date: Wed, 22 Mar 2023 06:57:51 -0000	[thread overview]
Message-ID: <167946827194.13423.8429057057323563603@emeril.freedesktop.org> (raw)
In-Reply-To: <20230322065003.1758611-1-mauro.chehab@linux.intel.com>

== Series Details ==

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

== Summary ==

Pipeline status: FAILED.

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

build:tests-fedora has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/38527580):
  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:1679468075:step_script
  section_start:1679468075:cleanup_file_variables
  Cleaning up project directory and file based variables
  section_end:1679468076: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/38527582):
  [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 tools/i915-perf/i915-perf-reader.
  [1338/1342] Linking target tests/core_hotunplug.
  [1339/1342] Linking target tests/gem_barrier_race.
  [1340/1342] Linking target tests/perf.
  [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:1679468072:step_script
  section_start:1679468072:cleanup_file_variables
  Cleaning up project directory and file based variables
  section_end:1679468073:cleanup_file_variables
  ERROR: Job failed: exit code 1

== Logs ==

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


  parent reply	other threads:[~2023-03-22  6:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22  6:49 [igt-dev] [PATCH i-g-t v4 0/8] Build Xe test documentation Mauro Carvalho Chehab
2023-03-22  6:49 ` [igt-dev] [PATCH i-g-t v4 1/8] meson: build " Mauro Carvalho Chehab
2023-03-22  6:49 ` [igt-dev] [PATCH i-g-t v4 2/8] testplan: build also a PDF file with the testplan Mauro Carvalho Chehab
2023-03-22  6:49 ` [igt-dev] [PATCH i-g-t v4 3/8] meson.build: place gtk-doc dependencies check at the right place Mauro Carvalho Chehab
2023-03-22  6:49 ` [igt-dev] [PATCH i-g-t v4 4/8] meson: get rid of a future-deprecated warning Mauro Carvalho Chehab
2023-03-22  6:50 ` [igt-dev] [PATCH i-g-t v4 5/8] meson: get rid of tests/xe/meson.build Mauro Carvalho Chehab
2023-03-22  6:50 ` [igt-dev] [PATCH i-g-t v4 6/8] testplan/meson.build: cleanup dependency chain Mauro Carvalho Chehab
2023-03-22  6:50 ` [igt-dev] [PATCH i-g-t v4 7/8] testplan/meson.build: use join_paths() Mauro Carvalho Chehab
2023-03-22  6:50 ` [igt-dev] [PATCH i-g-t v4 8/8] testplan/meson.build: re-indent file Mauro Carvalho Chehab
2023-03-22  6:57 ` Patchwork [this message]
2023-03-22  7:26 ` [igt-dev] ✓ Fi.CI.BAT: success for Build Xe test documentation (rev3) Patchwork
2023-03-22 10:31 ` [igt-dev] ✓ Fi.CI.IGT: " 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=167946827194.13423.8429057057323563603@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 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.