From: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for series starting with [i-g-t,1/8] Dockerfile: Avoid messing with WORKDIR
Date: Tue, 3 Sep 2019 15:46:10 +0300 [thread overview]
Message-ID: <20190903124610.vms5uckypygumpar@ahiler-desk1.fi.intel.com> (raw)
In-Reply-To: <20190903114140.6071.85032@emeril.freedesktop.org>
On Tue, Sep 03, 2019 at 11:41:40AM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [i-g-t,1/8] Dockerfile: Avoid messing with WORKDIR
> URL : https://patchwork.freedesktop.org/series/66156/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_6825_full -> IGTPW_3411_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with IGTPW_3411_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_3411_full, please notify your bug team to allow them
> to document this new failure mode, which will reduce false positives in CI.
>
> External URL: https://patchwork.freedesktop.org/api/1.0/series/66156/revisions/1/mbox/
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in IGTPW_3411_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@gem_exec_schedule@pi-ringfull-bsd1:
> - shard-kbl: [PASS][1] -> [FAIL][2] +4 similar issues
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6825/shard-kbl7/igt@gem_exec_schedule@pi-ringfull-bsd1.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3411/shard-kbl2/igt@gem_exec_schedule@pi-ringfull-bsd1.html
>
> * igt@gem_exec_suspend@basic-s4-devices:
> - shard-snb: [PASS][3] -> [FAIL][4]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6825/shard-snb2/igt@gem_exec_suspend@basic-s4-devices.html
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3411/shard-snb5/igt@gem_exec_suspend@basic-s4-devices.html
>
> * igt@i915_pm_rpm@debugfs-read:
> - shard-hsw: [PASS][5] -> [FAIL][6] +4 similar issues
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6825/shard-hsw8/igt@i915_pm_rpm@debugfs-read.html
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3411/shard-hsw8/igt@i915_pm_rpm@debugfs-read.html
>
> * igt@perf_pmu@cpu-hotplug:
> - shard-kbl: [PASS][7] -> [TIMEOUT][8]
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6825/shard-kbl6/igt@perf_pmu@cpu-hotplug.html
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3411/shard-kbl2/igt@perf_pmu@cpu-hotplug.html
>
> * igt@perf_pmu@enable-race-rcs0:
> - shard-apl: [PASS][9] -> [TIMEOUT][10]
> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6825/shard-apl4/igt@perf_pmu@enable-race-rcs0.html
> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3411/shard-apl4/igt@perf_pmu@enable-race-rcs0.html
>
> * igt@perf_pmu@init-wait-rcs0:
> - shard-apl: [PASS][11] -> [FAIL][12] +8 similar issues
> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6825/shard-apl3/igt@perf_pmu@init-wait-rcs0.html
> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3411/shard-apl4/igt@perf_pmu@init-wait-rcs0.html
>
> * igt@perf_pmu@semaphore-wait-idle-rcs0:
> - shard-apl: NOTRUN -> [FAIL][13] +1 similar issue
> [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3411/shard-apl4/igt@perf_pmu@semaphore-wait-idle-rcs0.html
Cc: Martin
All false postitives. The series is touching only .gitlab-ci and
Dockerfiles.
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-09-03 12:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 8:36 [igt-dev] [PATCH i-g-t 1/8] Dockerfile: Avoid messing with WORKDIR Arkadiusz Hiler
2019-09-03 8:36 ` [igt-dev] [PATCH i-g-t 2/8] Dockerfile: Make sure that we use correct base image Arkadiusz Hiler
2019-09-03 8:36 ` [igt-dev] [PATCH i-g-t 3/8] .gitlab-ci: Remove dead code Arkadiusz Hiler
2019-09-03 8:36 ` [igt-dev] [PATCH i-g-t 4/8] .gitalb-ci: Use only the necessary tags Arkadiusz Hiler
2019-09-03 8:36 ` [igt-dev] [PATCH i-g-t 5/8] .gitlab-ci: Switch to podman/buildah/skopeo Arkadiusz Hiler
2019-09-03 8:37 ` [igt-dev] [PATCH i-g-t 6/8] Dockerfile: Clean package manager caches and squash images Arkadiusz Hiler
2019-09-03 8:38 ` [igt-dev] [PATCH i-g-t 7/8] .gitlab-ci: Don't pull images until they are needed Arkadiusz Hiler
2019-09-03 8:38 ` [igt-dev] [PATCH i-g-t 8/8] .gitlab-ci: Use true --prefix Arkadiusz Hiler
2019-09-03 9:10 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/8] Dockerfile: Avoid messing with WORKDIR Patchwork
2019-09-03 9:35 ` [igt-dev] [PATCH i-g-t 1/8] " Petri Latvala
2019-09-03 11:06 ` Arkadiusz Hiler
2019-09-03 11:41 ` [igt-dev] ✗ Fi.CI.IGT: failure for series starting with [i-g-t,1/8] " Patchwork
2019-09-03 12:46 ` Arkadiusz Hiler [this message]
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=20190903124610.vms5uckypygumpar@ahiler-desk1.fi.intel.com \
--to=arkadiusz.hiler@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