Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Free all DMC payloads

From: Petri Latvala <petri.latvala@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx]  ✗ Fi.CI.BAT:  failure for drm/i915: Free all DMC payloads
Date: Tue, 10 Aug 2021 12:43:52 +0300	[thread overview]
Message-ID: <YRJKWCFs6wUSSmql@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20210809220537.emw2bow5ztm3xz4q@ldmartin-desk2>

On Mon, Aug 09, 2021 at 03:05:37PM -0700, Lucas De Marchi wrote:
> On Mon, Aug 09, 2021 at 10:00:34PM +0000, Patchwork wrote:
> > == Series Details ==
> > 
> > Series: drm/i915: Free all DMC payloads
> > URL   : https://patchwork.freedesktop.org/series/93521/
> > State : failure
> > 
> > == Summary ==
> > 
> > CI Bug Log - changes from CI_DRM_10461 -> Patchwork_20789
> > ====================================================
> > 
> > Summary
> > -------
> > 
> >  **FAILURE**
> > 
> >  Serious unknown changes coming with Patchwork_20789 absolutely need to be
> >  verified manually.
> > 
> >  If you think the reported changes have nothing to do with the changes
> >  introduced in Patchwork_20789, please notify your bug team to allow them
> >  to document this new failure mode, which will reduce false positives in CI.
> > 
> >  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20789/index.html
> > 
> > Possible new issues
> > -------------------
> > 
> >  Here are the unknown changes that may have been introduced in Patchwork_20789:
> > 
> > ### IGT changes ###
> > 
> > #### Possible regressions ####
> > 
> >  * igt@core_hotunplug@unbind-rebind:
> >    - fi-rkl-guc:         [PASS][1] -> [DMESG-WARN][2]
> >   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10461/fi-rkl-guc/igt@core_hotunplug@unbind-rebind.html
> >   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20789/fi-rkl-guc/igt@core_hotunplug@unbind-rebind.html
> 
> <Error>
> <Code>AccessDenied</Code>
> <Message>Access Denied</Message>
> <RequestId>H0EEPVCR70HST0VN</RequestId>
> <HostId>493NvO3WzGD1zhkvRRk6un+6HruE4hYwXX3W4OCSZWpluozyHRqL5h3rprp7q7erF2wu5xQa0is=</HostId>
> </Error>
> 
> ???
> 
> I noticed this happening sometimes and working after some minutes/hours.
> Is there a perm going out of sync on CI systems?

Because of reasons, the patchwork post happens before syncing the
files to AWS. The file sync can fail or take an undetermined amount of
time so it's done asynchronously. Typically the files get synced
within around 2 minutes of posting to patchwork but sometimes (~once a
month) sync fails and the files get there as part of the next test
result sync job.

-- 
Petri Latvala