On Thu, 17 Mar 2016 08:57:23 +0100, Tomi Sarvela wrote: > > On Wednesday 16 March 2016 16:40:24 Takashi Iwai wrote: > > On Wed, 16 Mar 2016 16:37:06 +0100, Daniel Vetter wrote: > > > On Wed, Mar 16, 2016 at 02:37:24PM +0200, Tomi Sarvela wrote: > > > > > > > > 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. > > > > Sorry about that, but I couldn't get the warning on my machine. > > > > How is the procedure to reproduce the bug? Please give the exact > > commit id and environment you're testing, too. > > Our CI has been built to mimic user environment, so base is up-to-date Ubuntu > 15.04. This affects to boot-up mechanics and usermode software versions. There > are about dozen machines, 8 gens, from ILK to SKL. > > Reproduction: CI is doing these steps > > - Compile kernel: CI_DRM is drm-intel-nightly HEAD > - Deploy it to testhost: copy to /boot, recreate initrd > - Boot testhost to init 3 > - Run newest IGT/piglit with basic testset > - Collect results > > The last commits tested are: > > CI_DRM_1140 git://anongit.freedesktop.org/drm-intel > 3e5ecc8c5ff80cb1fb635ce1cf16b7cd4cfb1979 > > CI_DRM_1141 git://anongit.freedesktop.org/drm-intel > fc881ebd9c3c26919c7d1113f8bf7014e1a05563 > > CI_DRM_1142 git://anongit.freedesktop.org/drm-intel > 9f8709ffd099e85e5e116ed7d09f1b8009f40847 > > CI_DRM_1143 git://anongit.freedesktop.org/drm-intel > 5356c22379fc96cb087ee59bfdbbe46ec3bdf654 > > CI_DRM_1144 git://anongit.freedesktop.org/drm-intel > a5c43f5d1b4968a370f54bdda5387ce213aca785 > > CI_DRM_1145 git://anongit.freedesktop.org/drm-intel > bf3dcd53821a7d6c81f7061c6c7956aad57ec615 > > CI_DRM_1146 git://anongit.freedesktop.org/drm-intel > be0d1481fb1a2fd1cb199b81c9c01154a78d43dd > > CI_DRM_1147 git://anongit.freedesktop.org/drm-intel > dbbc6d276864d7b7a3a1edb04f0511153f9c3852 > > Note that drm-intel-nightly history changes, so the exact commits might not be > there any more. Well, I have no internal access, so I have no idea which one succeeded and which one failed. Unfortunately I can't reproduce it in my side. A simpler unit test that can reliably reproduce the issue would be really appreciated... thanks, Takashi _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
