Closed Bug 846378 Opened 11 years ago Closed 11 years ago

"Exception: Test output exceeded timeout (60s)" in test-windows.testTrackWindows

Categories

(Add-on SDK Graveyard :: General, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: delimax, Assigned: mossop)

Details

Attachments

(1 file)

Test suite died.

$ ./mach --log-file jetpack-test-log jetpack-test

also of note: I'm using the github mirror of the source @ 
git://github.com/mozilla/mozilla-central.git

the build was a 64 bit one, mozconfig as such:

mk_add_options MOZ_OBJDIR=objdir-64-testing

ac_add_options --enable-debug
ac_add_options --enable-tests
ac_add_options --enable-mochitest
ac_add_options --enable-crashreporter

ac_add_options --disable-updater

ac_add_options --target=x86_64-pc-mingw32
ac_add_options --host=x86_64-pc-mingw32

I've got master checked out at de228fdbc36dacf810622ad47c791bb37fd6a90a

Logfile attached.
Let me know if there's some other info required.
Component: Build Config → General
Product: Firefox → Add-on SDK
Summary: './mach jetpack-test' fails on mozilla-central → "Exception: Test output exceeded timeout (60s)" in test-windows.testTrackWindows
Version: Trunk → unspecified
Assignee: nobody → dtownsend+bugmail
I don't have access to a 64-bit build so maybe you could answer a few questions before I dig in too much here:

Is this consistently reproducable?

Do you see the same issue if you run "make jetpack-tests" from the objdir?

Do you see the same issue with 32-bit builds?
Reopen if you can still reproduce this.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: