Closed Bug 708056 Opened 14 years ago Closed 14 years ago

Show a readable validation error when it times out

Categories

(addons.mozilla.org Graveyard :: Add-on Validation, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kumar, Assigned: basta)

Details

When validation times out, a RuntimeError exception gets raised. We should catch this and return readable message to the user so they know what happened. Current hotfix for timeouts is here (thanks Matt for the signal idea) https://github.com/mozilla/amo-validator/compare/60eb9218637095781c3ea13099dfccd7aeb747e4...84cf737f676e9135536f209a7c7e2fe889f528f1
Assignee: nobody → mattbasta
Priority: -- → P2
Target Milestone: --- → 6.3.5
Target Milestone: 6.3.5 → 6.3.6
Working on this. The only concern I have is that we can get RuntimeErrors during JS validation, namely when Spidermonkey can't be accessed or is too old. https://github.com/mozilla/amo-validator/blob/master/validator/testcases/javascript/spidermonkey.py Would it be wise to create a new exception type? Perhaps SpidermonkeyError?
Yes, please change my quick and dirty RuntimeError('time out') hack to ValidationTimeout() or something better. It was not meant as a permanent fix.
Hi Matt, thanks for the patch. Not sure if you saw my other comment on the pull, can you make separate pull requests per bug? That makes it way easier to prioritize when there are a lot of bugs to r and merge in.
Yeah, no problem. I got your message after I'd pushed this one. Do you want me to go back and rebase this onto its own branch? The only reason I was clumping these was because the Jetpack submodule makes a load of tests fail (paths changed in the recent SDK versions).
don't worry about rebasing
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.