All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "Latvala, Petri" <petri.latvala@intel.com>,
	Jessica Zhang <quic_jesszhan@quicinc.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] ✗ GitLab.Pipeline: warning for meson: Move MSM-specific tests to their own subdirectory (rev5)
Date: Mon, 25 Apr 2022 06:23:07 +0000	[thread overview]
Message-ID: <d22b812b1140465885b28af31638713f@intel.com> (raw)
In-Reply-To: <YmKTxenDlaT4VeXF@platvala-desk.ger.corp.intel.com>

Looks like rev 5 is re-reported.

Lakshmi.

-----Original Message-----
From: Latvala, Petri <petri.latvala@intel.com> 
Sent: Friday, April 22, 2022 4:39 AM
To: Jessica Zhang <quic_jesszhan@quicinc.com>
Cc: Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>; igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ GitLab.Pipeline: warning for meson: Move MSM-specific tests to their own subdirectory (rev5)

On Thu, Apr 21, 2022 at 03:40:39PM -0700, Jessica Zhang wrote:
> Hey Lakshmi,
> 
> I've looked over this failure, but it doesn't seem to be related to my 
> change.
> 
> Can you help take a look?

It's a spurious error that happens more and more often now... I just sent a patch to disable ninja-test-arm* temporarily to avoid this, until it's properly fixed.


--
Petri Latvala


> 
> Thanks,
> 
> Jessica Zhang
> 
> On 4/21/2022 2:06 PM, Patchwork wrote:
> > == Series Details ==
> > 
> > Series: meson: Move MSM-specific tests to their own subdirectory (rev5)
> > URL   : https://patchwork.freedesktop.org/series/102844/
> > State : warning
> > 
> > == Summary ==
> > 
> > Pipeline status: FAILED.
> > 
> > see https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/566172 for the overview.
> > 
> > test:ninja-test-arm64 has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/21593547):
> >    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:1650574984:step_script
> >    section_start:1650574984: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=21593547 responseStatus=201 Created token=PeHyNtwf
> >    section_end:1650574997:upload_artifacts_on_failure
> >    section_start:1650574997:cleanup_file_variables
> >    Cleaning up project directory and file based variables
> >    section_end:1650574998:cleanup_file_variables
> >    ERROR: Job failed: exit code 1
> > 
> > == Logs ==
> > 
> > For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/566172

  reply	other threads:[~2022-04-25  6:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 17:28 [igt-dev] [PATCH i-g-t v3] meson: Move MSM-specific tests to their own subdirectory Jessica Zhang
2022-04-21 20:36 ` [igt-dev] ✗ Fi.CI.BAT: failure for meson: Move MSM-specific tests to their own subdirectory (rev4) Patchwork
2022-04-21 21:06 ` [igt-dev] ✗ GitLab.Pipeline: warning for meson: Move MSM-specific tests to their own subdirectory (rev5) Patchwork
2022-04-21 22:40   ` Jessica Zhang
2022-04-22 11:38     ` Petri Latvala
2022-04-25  6:23       ` Vudum, Lakshminarayana [this message]
2022-04-21 22:43   ` Jessica Zhang
2022-04-22  5:19     ` Sai Nandan, YedireswarapuX
2022-04-21 21:36 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2022-04-22  2:10 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2022-04-22  4:56 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
2022-04-22  5:26 ` Patchwork
2022-04-25 19:00 ` [igt-dev] [PATCH i-g-t v3] meson: Move MSM-specific tests to their own subdirectory Abhinav Kumar

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=d22b812b1140465885b28af31638713f@intel.com \
    --to=lakshminarayana.vudum@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@intel.com \
    --cc=quic_jesszhan@quicinc.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.