Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Windows SeaMonkey 2.0 is perma-orange on browser_ApplicationPrefs.js, since bug 504021 landing

RESOLVED FIXED in mozilla1.9.3a1

Status

()

Core
Security
--
major
RESOLVED FIXED
8 years ago
8 years ago

People

(Reporter: sgautherie, Assigned: sgautherie)

Tracking

(Depends on: 1 bug, Blocks: 1 bug, {regression, verified1.9.1})

1.9.1 Branch
mozilla1.9.3a1
x86
Windows Server 2003
regression, verified1.9.1
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(status1.9.2 .1-fixed, status1.9.1 .8-fixed)

Details

(Whiteboard: [worked around by bug 534647 patch D])

(Assignee)

Description

8 years ago
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey2.0/1264087523.1264095152.30747.gz
WINNT 5.2 comm-1.9.1 unit test on 2010/01/21 07:25:23
moz:16764ab59892
Pass

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey2.0/1264101269.1264109989.7953.gz
WINNT 5.2 comm-1.9.1 unit test on 2010/01/21 11:14:29
moz:2ad3dc1dcf42
{
TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/suite/smile/test/browser_ApplicationPrefs.js | Timed out
}

This could be a coincidence(!) as SeaMonkey 2.0 has bug 534647 (and Firefox is still green).
But each Windows build (which was green, as in random orange) fails since landing of
{
You are not authorized to access bug #504021.
}

Is it possible that there is a side-effect?
(Assignee)

Comment 1

8 years ago
Last (still failing) run as 'unit test' build:
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey2.0/1264177768.1264190829.7265.gz
WINNT 5.2 comm-1.9.1 unit test on 2010/01/22 08:29:28

First (still failing) run as 'mochitest-other' build:
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey2.0/1264191306.1264191398.13677.gz
WINNT 5.2 comm-1.9.1 test mochitest-other on 2010/01/22 12:15:06

Last (still failing) run as 'mochitest-other' build:
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey2.0/1264207347.1264207581.4104.gz
WINNT 5.2 comm-1.9.1 test mochitest-other on 2010/01/22 16:42:27

Then bug 534647 patch D worked around this failure.
R.Fixed ftb: we'll see when bug 533290 is fixed (and the workaround removed)...
Assignee: nobody → sgautherie.bz
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
status1.9.1: --- → .8-fixed
status1.9.2: --- → .1-fixed
Depends on: 533290
Flags: in-testsuite-
Resolution: --- → FIXED
Whiteboard: [worked around by bug 534647 patch D]
Target Milestone: --- → mozilla1.9.3a1
Looks good on 1.9.1. Marking as verified fixed.
Keywords: verified1.9.1
You need to log in before you can comment on or make changes to this bug.