Closed
Bug 464027
Opened 16 years ago
Closed 15 years ago
There should be at least one 64 bit linux tbox running tests
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 520722
People
(Reporter: smaug, Unassigned)
References
Details
Currently 64 bit linux tboxes don't run tests and can't capture problems like bug 464010. There have been also other 64bit specific problems.
Updated•16 years ago
|
Component: Release Engineering → Release Engineering: Future
(In reply to comment #0) > There have been also other 64bit specific problems. e.g., bug 445626, bug 465088
If this were fixed, we might not have 64-bit Linux builds that crash on startup this morning (bug 510522)... preventing developers from developing on what may be our third largest development platform (i.e., after Windows/x86 and Mac OS X/x86 ... and possibly ahead of Linux/x86 and Mac OS X/ppc).
Updated•15 years ago
|
Blocks: support-L64
Comment 3•15 years ago
|
||
Do we know if unittests can even be run manually on a linux64 build?
Reporter | ||
Comment 4•15 years ago
|
||
I run mochitest/browser-chrome/chrome/crashtest/reftest pretty often on (debug) linux64 build. (I do need to disable tests which trigger bug 498380)
Reporter | ||
Comment 5•15 years ago
|
||
oh, and occasionally I run also some xpcshell tests. Have to admit it has been awhile when I last time run crashtest or reftest.
I've run reftest and crashtest; there's one crashtest that hangs on my machine, and I think it *might* be related to the fact that my machine is 64-bit, but it could be some other characteristic of my machine.
Comment 7•15 years ago
|
||
Is this a DUP of bug#520722?
No longer blocks: support-L64
Depends on: support-L64
Comment 9•14 years ago
|
||
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•