Closed
Bug 1108554
Opened 10 years ago
Closed 10 years ago
Addon validation timeouts on lightning linux beta
Categories
(addons.mozilla.org Graveyard :: Add-on Validation, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
2015-01
People
(Reporter: magopian, Assigned: davidbgk)
Details
Attachments
(2 files)
Seems like the increased size of the latest lightning linux beta (4.4Mb) is enough to go past the addon validation timeout.
The message displayed when uploading the addon is the following:
"your addon failed validation with 1 error: Validation timed out."
This doesn't happen each time, sometimes, retrying will get through.
Bug created on behalf of :Fallen
Comment 2•10 years ago
|
||
Note that bug 1108343 is for a similar problem, so there might be something else going on.
Comment 3•10 years ago
|
||
ReminderFox 2.1.5.1 addon exhibiting AMO Update Validation timeout.
Comment 4•10 years ago
|
||
ReminderFox is another addon that was experiencing timeouts when I tried to upload between December 6-8. I keep getting:
the validation is failing due to:
"Validation timed out. Error: The validation process took too long to complete. Contact an addons.mozilla.org editor for more information.
Validation timeout after 90 seconds"
ReminderFox is quite large (> 1MB), but the validation never timed out before. Perhaps there's additional validation processing that takes longer now.
See attached version of the addon.
Assignee | ||
Comment 5•10 years ago
|
||
https://github.com/mozilla/olympia/commit/eb5001adfc4042a34663b1c84c6c3f578021aade
We need to improve the performances of the amo-validator but that's a huge work so it'll not be for that push. Let's see if increasing the validation timeout is enough for now.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 6•10 years ago
|
||
We had a similar bug on zamboni that was being caused by using django's transaction middleware. It was fixed in bug 1108462. I did a grep of olympia when I saw that and didn't see the transaction middleware but just commenting in case the timeout bump doesn't fix this.
Comment 7•10 years ago
|
||
Verified with the attached addon and the timeout issue is not reproducible anymore : http://screencast.com/t/7ehNps3aX1n
Status: RESOLVED → VERIFIED
Comment 8•10 years ago
|
||
Comment 9•10 years ago
|
||
While it might work for 1.23mb, it still does not work for the originally reported addon, which is much larger. It is still an issue for me. Please set the timeout accordingly, I really want to get this addon out asap because 3.6b1 and b2 is totally broken for Seamonkey.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 10•10 years ago
|
||
We have planned a push to production of the fix for today... if everything goes as expected, you should be able to test again soon.
Reporter | ||
Comment 11•10 years ago
|
||
The push is done, so feel free to try again, and please let us know if it fixed now.
Comment 12•10 years ago
|
||
Great, that seemed to have worked! I've managed to upload all 3.6b3 packages. Thank you so much :)
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 13•10 years ago
|
||
Happy that it worked, thanks David again for fixing that!
Reporter | ||
Updated•10 years ago
|
Target Milestone: 2014-12 → 2015-01
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•