canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
(Update current status.) |
(TUnit Mac TB now ok, Windows build continuously failing.) |
||
| Line 45: | Line 45: | ||
** <strike>TUnit Linux failure similar to gconf error seen before - gozer to fix</strike> | ** <strike>TUnit Linux failure similar to gconf error seen before - gozer to fix</strike> | ||
*** <strike>{{bug|444818}} is back, and something in the new build system wipes local tree changes, so it would be better if the suggested patch could land soon.</strike> | *** <strike>{{bug|444818}} is back, and something in the new build system wipes local tree changes, so it would be better if the suggested patch could land soon.</strike> | ||
** TUnit Mac, one failure in test_nsIMsgFolderListenerLocal.js, possible timeout - Standard8 couldn't reproduce, new build set going. gozer: definitely timing related, as playing with the timeout value makes the bug appear/dissapear. I've seen the test pass with a timeout of 6s. | ** <strike>TUnit Mac, one failure in test_nsIMsgFolderListenerLocal.js, possible timeout - Standard8 couldn't reproduce, new build set going. gozer: definitely timing related, as playing with the timeout value makes the bug appear/dissapear. I've seen the test pass with a timeout of 6s.</strike> | ||
** | ** Windows build continuously failing. | ||
** '''Builds fail when mozilla-central triggers build''' | ** '''Builds fail when mozilla-central triggers build''' | ||