User:Dbaron/Progress on hidden unit tests: Difference between revisions
Jump to navigation
Jump to search
(bump heading levels) |
|||
Line 26: | Line 26: | ||
== Windows 7 / reftest-d2d == | == Windows 7 / reftest-d2d == | ||
Still | Still too many failures to track. A decent number are {{bug|578116}} (border beveling), but there are a lot of others. |
Revision as of 18:51, 31 July 2010
Some unit tests on supported or soon-to-be-supported platforms are permanently failing, and are therefore hidden from showing up on tinderbox. This page tracks the bugs for those failures.
Mac OS X 10.6 / 64-bit
The following bugs need to be fixed for all the Mac OS X 10.6 / 64-bit unit tests to be green. (It's not clear whether these are 10.6-specific or 64-bit specific.)
- bug 561350 - test_punicodeURIs.js - needs somebody to debug
Windows 7 / 32-bit
The following bugs need to be fixed for all standard Windows 7 unit tests to be green:
- bug 562955 - test_bug458898.html - probably a windows widget code bug
- bug 581734 - test_bug558403.html - needs somebody to debug
- bug 582315 - test_taskbarprogress_downloadstates.xul - a Windows-7-specific test that's intermittently orange at high rates
Windows 7 / 64-bit
The following bugs need to be fixed for all Windows7 / 64-bit unit tests to be green:
- the bugs above for Windows 7 / 32-bit
- bug 582850 - known failures markings due to Win32 assembly in JPEG code incorrectly apply to Win64
- bug 582910 - increase stack size to match JS stack limit
- test_ctypes.xul timeout
- maybe other bugs hidden by the above?
Windows 7 / reftest-d2d
Still too many failures to track. A decent number are bug 578116 (border beveling), but there are a lot of others.