buildbot status: 33 hours since last spurious message

Dan Kegel dank at kegel.com
Thu Oct 13 01:13:19 CDT 2011


Valid warnings sent:
- 79847: shell32/tests: Better check the result of SHGetDesktopFolder
(minor type-safety warning)
- 79851: wined3d: Report every texture format as filterable and
blendable. (interesting d3d failure on nvidia hardware)
- 79857: [2/3] gdi32: remove PS_USERSTYLE FIXME and work-arounds (take
3) - patch sequence error
- 79869: [2/4] gdi32: remove PS_USERSTYLE FIXME and work-arounds (take
4) - patch sequence error

I checked in a probably-usable valgrind mode, and am trying it out on
a private bot.
Since it's compiing with -O1 instead of -O0, just the compiling phase is
finding a few "possibly uninitialised" warnings:
 mesh.c:3441:20: error: ‘current_frame’ may be used uninitialized in
this function
 texture.c:953:11: error: ‘comp_value’ may be used uninitialized in
this function
 texture.c:1087:11: error: ‘comp_value’ may be used uninitialized in
this function
 texture.c:1190:11: error: ‘comp_value’ may be used uninitialized in
this function
 msi.c:353:10: error: ‘r’ may be used uninitialized in this function
 xdr.c:516:36: error: ‘xsd_child’ may be used uninitialized in this function
so I'm filing bugs, e.g. http://bugs.winehq.org/show_bug.cgi?id=28689
and am collecting a bunch of foo-placate-bar.patch's to work around this.

Last spurious message was 33 hours ago, for patch 79793.



More information about the wine-tests-results mailing list