All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Bhanuprakash Modem" <bhanuprakash.modem@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ GitLab.Pipeline: warning for intel-ci: Drop kms_setmode@basic-clone-single-crtc from BAT
Date: Tue, 12 Apr 2022 11:15:42 -0000	[thread overview]
Message-ID: <164976214206.18367.4666602456251402328@emeril.freedesktop.org> (raw)
In-Reply-To: <20220412104616.1669124-1-bhanuprakash.modem@intel.com>

== Series Details ==

Series: intel-ci: Drop kms_setmode@basic-clone-single-crtc from BAT
URL   : https://patchwork.freedesktop.org/series/102591/
State : warning

== Summary ==

Pipeline status: FAILED.

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

test:ninja-test-arm64 has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/21081671):
  Ok:                   22
  Expected Fail:         3
  Fail:                289
  Unexpected Pass:       0
  Skipped:               0
  Timeout:               0
  
  Full log written to /builds/gfx-ci/igt-ci-tags/build/meson-logs/testlog.txt
  section_end:1649761992:step_script
  section_start:1649761992:upload_artifacts_on_failure
  Uploading artifacts for failed job
  Uploading artifacts...
  build: found 1724 matching files and directories   
  Uploading artifacts as "archive" to coordinator... 201 Created  id=21081671 responseStatus=201 Created token=Mj7tMdYT
  section_end:1649762003:upload_artifacts_on_failure
  section_start:1649762003:cleanup_file_variables
  Cleaning up project directory and file based variables
  section_end:1649762004:cleanup_file_variables
  ERROR: Job failed: exit code 1
  

test:ninja-test-armhf has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/21081670):
  Ok:                   22
  Expected Fail:         3
  Fail:                289
  Unexpected Pass:       0
  Skipped:               0
  Timeout:               0
  
  Full log written to /builds/gfx-ci/igt-ci-tags/build/meson-logs/testlog.txt
  section_end:1649761992:step_script
  section_start:1649761992:upload_artifacts_on_failure
  Uploading artifacts for failed job
  Uploading artifacts...
  build: found 1725 matching files and directories   
  Uploading artifacts as "archive" to coordinator... 201 Created  id=21081670 responseStatus=201 Created token=-MYr3u-q
  section_end:1649762002:upload_artifacts_on_failure
  section_start:1649762002:cleanup_file_variables
  Cleaning up project directory and file based variables
  section_end:1649762002:cleanup_file_variables
  ERROR: Job failed: exit code 1

== Logs ==

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

  reply	other threads:[~2022-04-12 11:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 10:46 [igt-dev] [PATCH] intel-ci: Drop kms_setmode@basic-clone-single-crtc from BAT Bhanuprakash Modem
2022-04-12 11:15 ` Patchwork [this message]
2022-04-12 11:38 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2022-04-12 11:55 ` [igt-dev] [PATCH] " Petri Latvala
2022-04-12 14:37   ` Modem, Bhanuprakash
2022-04-12 14:55     ` Petri Latvala
2022-04-12 13:41 ` [igt-dev] ✓ Fi.CI.IGT: success for " 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=164976214206.18367.4666602456251402328@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=bhanuprakash.modem@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 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.