On Wed, Mar 16, 2016 at 4:50 PM, Jani Nikula <jani.nikula@xxxxxxxxxxxxxxx> wrote: > On Wed, 16 Mar 2016, Daniel Vetter <daniel@xxxxxxxx> wrote: >> [ text/plain ] >> On Wed, Mar 16, 2016 at 02:37:24PM +0200, Tomi Sarvela wrote: >>> On Wednesday 16 March 2016 10:48:43 Imre Deak wrote: >>> > Tomi, noticed two things that maybe infrastructure related, see below: >>> > >>> > > Test drv_module_reload_basic: >>> > > skip -> PASS (bdw-nuci7) >>> > > Test gem_ringfill: >>> > > Subgroup basic-default-s3: >>> > > pass -> DMESG-WARN (skl-nuci5) >>> > > Test gem_storedw_loop: >>> > > Subgroup basic-bsd: >>> > > pass -> DMESG-WARN (skl-nuci5) >>> > > Subgroup basic-bsd1: >>> > > pass -> DMESG-WARN (skl-nuci5) >>> > >>> > Unrelated platform. All of the above are SND resume failures. Ville >>> > said he contacted Takashi about them. >>> >>> SND is recurring problem. I'd like to see drm-intel-nightly not breaking when >>> pulling sound updates. >> >> We need to escalate this again, snd team seriously sucks at quality >> control :( Adding Libin&Takashi. If this doesn't improve I need to throw >> sound trees out of -nightly for real. > > With that, we'd get more stable CI, but we'd also only see the failures > once the sound trees get merged upstream. We don't want that either. > > One idea would be to have separate CI runs for updating trees not in our > control. But we're pretty far from making that happen. Yes agreed, it would probably not help a lot at all to drop sound trees, we'd simply notice a bit later. I'm not sure what would be the best option here, just expressing maintainer grumpiness ;-) Good ideas very much welcome ... -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
