Closed
Bug 744717
Opened 12 years ago
Closed 12 years ago
Fennec runs are not accessible in litmus
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: AdrianT, Assigned: cshields)
References
Details
Steps to reproduce: 1. Go to https://litmus.mozilla.org. 2. Select "log in". 3. Select "Run Tests". 4. Choose one of the Fennec Catch-all test runs. 5. Enter a testid, os and os version and submit the configuration. Expected results: The test run with the selected configuration is created. Actual results: A timeout error is returned. Other test runs like "firefox sync catch-all" run work. Notes: The runs can be managed and they are enabled but we can't access them.
Updated•12 years ago
|
Severity: critical → blocker
Comment 1•12 years ago
|
||
Dropping the severity on this. While I do see this behavior, it's intermittent here. If I reload/resend once or twice, the testgroup/subgroup selection page loads for me. I'm not sure why this would be, perhaps the zeus load balancer that's in front of this machine now is causing it? I've put that question to IT.
Severity: blocker → critical
Comment 2•12 years ago
|
||
This is blocking our testing of Fennec.
Updated•12 years ago
|
Assignee: nobody → server-ops
Component: Litmus → Server Operations
Product: Webtools → mozilla.org
QA Contact: litmus → phong
Version: Trunk → other
Assignee | ||
Comment 3•12 years ago
|
||
(In reply to Chris Cooper [:coop] from comment #1) > I'm not sure why this would be, perhaps the zeus load balancer that's in > front of this machine now is causing it? I've put that question to IT. Only thing I can think of would be the timeout values in the pool and virtual server (set to 30 and 40 secs respectively). I've bumped all of these to 300. Let me know if this does not fix the problem.
Assignee: server-ops → cshields
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•12 years ago
|
||
Issue seems to have been fixed now. We are able to access the runs. Will reopen the issue/log new issues if we run in other problems but runs seem to be accessible now.
Status: RESOLVED → VERIFIED
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•