On Mon, 13 Mar 2017, Daniel Vetter <daniel@xxxxxxxx> wrote: > On Thu, Mar 09, 2017 at 12:48:56PM +0200, Jani Nikula wrote: >> On Thu, 09 Mar 2017, Daniel Vetter <daniel@xxxxxxxx> wrote: >> > On Wed, Mar 01, 2017 at 10:52:35AM -0000, Patchwork wrote: >> >> == Series Details == >> >> >> >> Series: series starting with [1/6] drm/i915: Use drm_connector_list_iter in debugfs >> >> URL : https://patchwork.freedesktop.org/series/20441/ >> >> State : failure >> >> >> >> == Summary == >> >> >> >> Series 20441v1 Series without cover letter >> >> https://patchwork.freedesktop.org/api/1.0/series/20441/revisions/1/mbox/ >> >> >> >> Test gem_ctx_create: >> >> Subgroup basic-files: >> >> pass -> INCOMPLETE (fi-bdw-5557u) >> >> Test kms_busy: >> >> Subgroup basic-flip-default-a: >> >> fail -> PASS (fi-byt-n2820) >> >> Test kms_pipe_crc_basic: >> >> Subgroup nonblocking-crc-pipe-a: >> >> pass -> DMESG-WARN (fi-byt-n2820) >> > >> > Thrown at trybot to confirm these are unrelated flukes and merged with >> > Maarten's irc-r-b for the remaining patches. >> >> You should be able to request a re-run from the patchwork >> interface. It's well hidden, but it's there somewhere... > > I quickly looked, didn't find it, trybot was easier (but annoying that the > priority is lower and the queue almost always full until Europe goes to > sleep). The downside with sending to trybot is that if you push the patches that were actually tested, they'll get a broken Link: tag. Figured it out. You need to go to the series view, select the series you want to test, and after that a "Test again" button will show up at the top. (Yes. Don't get me started.) BR, Jani. -- Jani Nikula, Intel Open Source Technology Center _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
