Closed
Bug 1020262
Opened 10 years ago
Closed 10 years ago
Fix fireplace tests
Categories
(Marketplace Graveyard :: Consumer Pages, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
2014-06-10
People
(Reporter: mat, Assigned: mat)
Details
(Whiteboard: [repoman][qa-])
Fireplace tests have been broken for a while, since https://github.com/mozilla/fireplace/commit/e5aa13992417e26466c94e72b7295b92c37312b8 according to travis history (https://travis-ci.org/mozilla/fireplace/builds)
Let's fix that.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → mpillard
Status: NEW → ASSIGNED
Whiteboard: [repoman] → [repoman][qa-]
Assignee | ||
Comment 1•10 years ago
|
||
Pretty sure https://github.com/diox/flue/commit/08fe44f6d57638e2c4a2f2b6d7df530736e8f60f will fix it - it fixes the failures for me locally. We just need to update the flue instance on stackato and get npmjs.org to stop returning 503s...
Assignee | ||
Comment 2•10 years ago
|
||
We also needed to wait a bit after logout: https://github.com/mozilla/fireplace/commit/71732a508a424bb37dbbf96d8ecf7cfa253d0cdc
Assignee | ||
Comment 3•10 years ago
|
||
Fixed for good in https://github.com/mozilla/fireplace/commit/50cca27cf3cf5353c299500d81b13b6b1906902b
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 4•10 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•