On Mon, Jan 11, 2016 at 02:50:28PM +0200, Mika Kuoppala wrote: > Patchwork <patchwork@xxxxxxxxxxxxxxxxxxxxxxxx> writes: > > > == Summary == > > > > Built on ff88655b3a5467bbc3be8c67d3e05ebf182557d3 drm-intel-nightly: 2016y-01m-11d-07h-30m-16s UTC integration manifest > > > > Test gem_storedw_loop: > > Subgroup basic-render: > > pass -> DMESG-WARN (skl-i5k-2) UNSTABLE > > dmesg-warn -> PASS (bdw-ultra) > > Test kms_flip: > > Subgroup basic-flip-vs-dpms: > > dmesg-warn -> PASS (ilk-hp8440p) > > Subgroup basic-flip-vs-modeset: > > pass -> DMESG-WARN (skl-i5k-2) > > dmesg-warn -> PASS (bsw-nuc-2) > > pass -> DMESG-WARN (ilk-hp8440p) > > dmesg-warn -> PASS (byt-nuc) > > Subgroup basic-flip-vs-wf_vblank: > > pass -> DMESG-WARN (byt-nuc) > > Subgroup basic-plain-flip: > > dmesg-warn -> PASS (bsw-nuc-2) > > dmesg-warn -> PASS (byt-nuc) > > Test kms_pipe_crc_basic: > > Subgroup nonblocking-crc-pipe-b: > > pass -> DMESG-WARN (byt-nuc) > > Subgroup nonblocking-crc-pipe-c: > > pass -> DMESG-WARN (bsw-nuc-2) > > Subgroup read-crc-pipe-a: > > dmesg-warn -> PASS (byt-nuc) > > Subgroup read-crc-pipe-b: > > dmesg-warn -> PASS (byt-nuc) > > Subgroup read-crc-pipe-b-frame-sequence: > > pass -> DMESG-WARN (bdw-ultra) > > dmesg-warn -> PASS (byt-nuc) > > Subgroup read-crc-pipe-c: > > dmesg-warn -> PASS (bsw-nuc-2) > > Subgroup read-crc-pipe-c-frame-sequence: > > pass -> DMESG-WARN (bsw-nuc-2) But what with all the pass->dmesg-warn changes above? That's considered BAT failure too, we can't afford to sprinkle warnings all over ... And it's a bunch of different machines. > > Test pm_rpm: > > Subgroup basic-pci-d3-state: > > dmesg-warn -> PASS (byt-nuc) > > > > bdw-ultra total:138 pass:130 dwarn:1 dfail:0 fail:1 > > skip:6 > > Tomi suspected this as a fluke fail. There was no igt stdout nor stderr > for this case. We did a rerun and bdw-ultra passed. > > -Mika > > > bsw-nuc-2 total:141 pass:115 dwarn:2 dfail:0 fail:0 skip:24 > > byt-nuc total:141 pass:122 dwarn:4 dfail:0 fail:0 skip:15 > > hsw-brixbox total:141 pass:134 dwarn:0 dfail:0 fail:0 skip:7 > > hsw-gt2 total:141 pass:137 dwarn:0 dfail:0 fail:0 skip:4 > > ilk-hp8440p total:141 pass:100 dwarn:4 dfail:0 fail:0 skip:37 > > skl-i5k-2 total:141 pass:130 dwarn:3 dfail:0 fail:0 skip:8 > > skl-i7k-2 total:141 pass:131 dwarn:2 dfail:0 fail:0 skip:8 > > snb-dellxps total:141 pass:122 dwarn:5 dfail:0 fail:0 skip:14 > > snb-x220t total:141 pass:122 dwarn:5 dfail:0 fail:1 skip:13 > > > > HANGED ivb-t430s in igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b So is killing a machine ... pretty sure this is new-ish. -Daniel > > > > Results at /archive/results/CI_IGT_test/Patchwork_1116/ > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@xxxxxxxxxxxxxxxxxxxxx > http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
