No spurious build failures for a whole week, and as soon as I re-enable
notifications we get one... :(
This is different from the winflexbison issue. It's te=he:
"Failed to provision build worker virtual machine in Google Compute
Engine cloud. Try restarting build later."
that happened once before.
I wish there was some way to tell Appveyor to retry automatically, or
not trigger notification for this. I'll have to dig into this and file
an issue.
I'll disbale notifications again..
Jose
On 16/12/15 17:57, AppVeyor wrote:
Build mesa 132 failed
<https://ci.appveyor.com/project/jrfonseca-fdo/mesa/build/132>
Commit 61cdb7665f by Neil Roberts <mailto:n...@linux.intel.com> on
12/16/2015 2:53 PM:
Revert "i965: Use MESA_FORMAT_B8G8R8X8_SRGB for RGB visuals"\n\nThis
reverts commit 839793680f99b8387bee9489733d5071c10f3ace.\n\nThe patch
was breaking DRI3 because driGLFormatToImageFormat does not\nhandle
MESA_FORMAT_B8G8R8X8_SRGB which ended up making it fail to\ncreate the
renderbuffer and it would later crash. It's not trivial to\nadd this
format because there is no __DRI_IMAGE_FORMAT nor\n__DRI_IMAGE_FOURCC
define for the format either. I'm not sure how\ndifficult adding this
would be and whether adding a new format would\nrequire some sort of new
version for DRI. Seeing as this might take a\nwhile to fix I think it
makes sense to just revert the patch in the\nmeantime in order to avoid
regressing master.\n\nIt is also not handled in
intel_gles3_srgb_workaround and there may be\nother cases where it
breaks.\n\nBugzilla:
https://bugs.freedesktop.org/show_bug.cgi?id=93388\nAcked-by: Jason
Ekstrand <jason.ekstr...@intel.com>
Configure your notification preferences
<https://ci.appveyor.com/notifications>
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
