Closed
Bug 564274
Opened 15 years ago
Closed 15 years ago
Rev3 Fedora12 orange: layout/reftests/bugs -> 456219-1a.html, 456219-1b.html and 456219-1c.html
Categories
(Core :: Layout: Block and Inline, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 559426
People
(Reporter: armenzg, Unassigned)
References
Details
Attachments
(1 file)
6.55 KB,
patch
|
Details | Diff | Splinter Review |
After disabling anti-aliasing in a test run on bug 558910 I got three test failures that were not tracked. These tests failures also exist when we don't disable anti-aliasing.
> REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/armenzg/reftest/tests/layout/reftests/bugs/456219-1a.html |
> REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/armenzg/reftest/tests/layout/reftests/bugs/456219-1b.html |
> REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/armenzg/reftest/tests/layout/reftests/bugs/456219-1c.html
Reporter | ||
Comment 1•15 years ago
|
||
Here is the log I mentioned:
https://bugzilla.mozilla.org/attachment.cgi?id=443935&action=edit
You can also read the comment that I posted here:
https://bugzilla.mozilla.org/show_bug.cgi?id=558910#c13
Reporter | ||
Updated•15 years ago
|
Blocks: ReftestFedoraOrange
Reporter | ||
Updated•15 years ago
|
No longer blocks: fedora-oranges
Comment 2•15 years ago
|
||
Reporter | ||
Comment 3•15 years ago
|
||
Jeff I tried testing this but I don't know if I did it right.
* push the change to the try server
* get the builds on the fedora slave
* use the packaged test from a build from tinderbox-builds (try server doesn't yet produce packaged tests)
* follow the same procedures as in https://bugzilla.mozilla.org/show_bug.cgi?id=558910#c13
If you want you can book one of the Fedora slaves and try to test it since I don't know if I am doing it right.
Otherwise, I will wait for the try as branch project to come online (it should have unit tests for try)
Comment 4•15 years ago
|
||
Fixed by the patches just pushed from bug 559426.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•