Re: Testsuite changes this week

On Wed, Jul 09, 2014 at 08:53:31PM +0000, Bryce W. Harrington wrote:
                   git     git     git     git      git
                  05/03   05/12   06/09   07/08    07/21
--------------------------------------------------------
Tests run:        24838   24838   24813   24812    24839
Passed:           15774   15743   16015   16001    16024
Failed:            6476    6505    6226    6224     6228
Expected Failed:    332     332     315     332      332
Error:                1       0       1       1        0
Crashed:             32      35      33      31       32
Untested:          2223    2223    2223    2223     2223
Total:            24838   24838   24813   24812    24839

Here's the tests that changed results since the previous run:

FAIL -> PASS # bitmap-font.gl-window.argb32
PASS -> FAIL # degenerate-path.gl-window.argb32
FAIL -> PASS # pass-through.gl-window.argb32
CRASHED -> FAIL # pthread-same-source.svg11.argb32
FAIL -> CRASHED # subsurface-modify-child.gl-window.argb32
ERROR -> FAIL # xcb-huge-image-shm.script.argb32

The degenerate-path test is a randomly failing test.

Bryce

> Here's the tests that changed results between last month and now:
> 
> FAIL -> PASS # degenerate-path.gl-window.argb32
> FAIL -> CRASHED # pthread-same-source.svg11.argb32
> CRASHED -> FAIL # pthread-same-source.svg11.rgb24
> FAIL -> PASS # rel-path.gl-window.argb32
> CRASHED -> FAIL # subsurface-modify-child.gl-window.argb32
> CRASHED -> FAIL # subsurface-modify-child.gl-window-msaa.argb32
> 
> pthread always randomly crashes/fails, and looking at last month, the
> gl-window tests seem to do similarly.  Perhaps the gl-window tests are
> the ones triggering OOM conditions?  Memory leak somewhere?
> 
> Anyway, the good news is that the past month's changes don't appear to
> have broken any tests.
> 
> Bryce
> 
> > Aside from downscale and pthread tests, these three tests also switched
> > from pass to fail on these two test runs:
> >
> > PASS -> FAIL # bitmap-font.gl-window.argb32
> > PASS -> FAIL # degenerate-path.gl-window.argb32
> > PASS -> FAIL # pass-through.gl-window.argb32
> >
> > It's interesting all three are with the gl-window backend, but otherwise
> > the three tests have little commonality.  It's not evident looking at
> > the test code why they'd be failing, and nothing in the git logs pops
> > out as directly relating to gl-window.  Anyone else seeing these three
> > tests failing now, but passing as of a month ago?
> >
> > Bryce
-- 
cairo mailing list
[email protected]
http://lists.cairographics.org/mailman/listinfo/cairo