Closed
Bug 983786
Opened 11 years ago
Closed 11 years ago
TEST-UNEXPECTED-FAIL | Layers.TextureSerialization on Windows debug builds
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: briansmith, Unassigned)
References
Details
With the patch in bug 883339 on my Windows debug build, with this mozconfig:
. $topsrcdir/browser/config/mozconfig
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../ff-dbg
ac_add_options --enable-debug
ac_add_options --disable-crashreporter
ac_add_options --enable-logging
ac_add_options --enable-tests
ac_add_options --enable-gtest
ac_add_options --disable-optimize
ac_add_options --enable-warnings-as-errors
export XMOZ_PSEUDO_DERECURSE=no-pymake
I get:
0:03.24 TEST-START | Layers.TextureSerialization
0:03.33 TEST-UNEXPECTED-FAIL | Layers.TextureSerialization | Value of: data2[y*stride2 + x*bpp + b]
0:03.33 Actual: '\xCD' (205)
0:03.33 Expected: data1[y*stride1 + x*bpp + b]
0:03.33 Which is: '\0' @ c:\p\firefox\src\gfx\tests\gtest\TestTextures.cpp:71
0:03.37 TEST-UNEXPECTED-FAIL | Layers.TextureSerialization | Value of: data2[y*stride2 + x*bpp + b]
0:03.37 Actual: '\xCD' (205)
0:03.37 Expected: data1[y*stride1 + x*bpp + b]
0:03.37 Which is: '\0' @ c:\p\firefox\src\gfx\tests\gtest\TestTextures.cpp:71
0:03.37 TEST-UNEXPECTED-FAIL | Layers.TextureSerialization | Value of: data2[y*stride2 + x*bpp + b]
0:03.37 Actual: '\xFF' (255)
0:03.37 Expected: data1[y*stride1 + x*bpp + b]
0:03.37 Which is: '\x3' (3) @ c:\p\firefox\src\gfx\tests\gtest\TestTextures.cpp:71
0:03.38 TEST-UNEXPECTED-FAIL | Layers.TextureSerialization | Value of: data2[y*stride2 + x*bpp + b]
0:03.38 Actual: '\xCD' (205)
0:03.38 Expected: data1[y*stride1 + x*bpp + b]
0:03.38 Which is: '\0' @ c:\p\firefox\src\gfx\tests\gtest\TestTextures.cpp:71
0:03.39 TEST-UNEXPECTED-FAIL | Layers.TextureSerialization | test completed (time: 173ms)
| Reporter | ||
Comment 1•11 years ago
|
||
This is WORKSFORME today with VS2013.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•