Closed
Bug 558782
(fedora_unittests)
Opened 15 years ago
Closed 14 years ago
Tracking bug for running unit tests on Fedora talos machines
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Unassigned)
References
Details
(Whiteboard: [talos][linux64][unittest])
There is too many bugs on bug 548768 and it is difficult to have the big
picture of each platform.
We can add the summary updates for Fedora and Fedora 64 in here.
The current status update is the following:
* We are running unit tests for both platforms for mozilla-central
* The permanent oranges are hidden and they are tracked in bug 554934
* We need more Rev3 machines to enable the unit tests on more branches
Reporter | ||
Updated•15 years ago
|
Priority: -- → P3
Comment 1•15 years ago
|
||
What's the current state?
I know that we are running fed/fed64 talos unit tests - have the linux build unit tests been disabled?
Reporter | ||
Comment 2•15 years ago
|
||
There's a couple of bugs that I have to deploy through puppet (gtk update and libm.so - bug 558521 and bug 558911). I should have those fixed next week.
We are not disabling unit tests on CentOS for mc until we are in good shape with the Fedora unit tests.
Let's reevaluate the state in a couple of weeks.
Reporter | ||
Comment 3•15 years ago
|
||
Update status:
* gtk update for bug 558521 has been deployed. This random-orange should be now fixed
Reporter | ||
Comment 4•15 years ago
|
||
(In reply to comment #3)
> Update status:
> * gtk update for bug 558521 has been deployed. This random-orange should be now
> fixed
This random-orange does not seem to occur anymore. This was affecting mainly M5.
* bug 474068 will soon be landing a fix that will allow us to enable M4
Updated•15 years ago
|
OS: Mac OS X → Linux
Whiteboard: [talos][linux64][unittest]
Comment 5•14 years ago
|
||
bug 557918 is only tracking Windows at this point. This is finished AFAIK.
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
•