There was a problem logging in to MozTrap which is described in Bug #1159104 The problem was due to browserid.org going away, which was a mistake, but it is to be decomissioned. Osmose indicated that updating to the most recent version of django-browserid would eliminate the possibility of the issue recurring.
Peter, would it be possible for you to fine some time to do this?
(In reply to Bob Silverberg [:bsilverberg] from comment #1) > Peter, would it be possible for you to fine some time to do this? Yes and no. I'd rather finished my quarterly goals first.
Sergey, would you have time/interest to tackle this?
Hey Stephen, I was in long vacation... Not sure I understood what that issue about, did not worked with MozTrap before, how can I help here?
(In reply to Sergey Tupchiy from comment #4) > Hey Stephen, > I was in long vacation... > Not sure I understood what that issue about, did not worked with MozTrap > before, how can I help here? Hey Sergey - sorry about that; was under the impression you have done, or would be interested in doing, Django-level upgrades - let us know if you'd be interested! (You'd have reviews/mentorship, and this is an important upgrade for us to have in the mid-to-long term.) Thanks!
Let's not cry wolf.
Severity: critical → normal
Mass-closing remaining MozTrap bugs as WONTFIX, due to 1) the Mozilla-hosted instance being decommissioned (see https://wiki.mozilla.org/TestEngineering/Testrail), and, for now, 2) the still-up code archived at its GitHub page: https://github.com/mozilla/moztrap (we'll decide what's next for that, in the near future). See also the history and more-detailed discussion which led us here, at https://groups.google.com/forum/#!topic/mozilla.dev.quality/Sa75hV8Ywvk (If you'd like, you should be able to filter these notification emails using at least the unique string of "Sa75hV8Ywvk" in the message body. Thanks!
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.