The default bug view has changed. See this FAQ.

Validation timeout tracebacks

VERIFIED FIXED in 2013-06-13

Status

addons.mozilla.org Graveyard
Add-on Validation
P1
normal
VERIFIED FIXED
4 years ago
a year ago

People

(Reporter: clouserw, Assigned: basta)

Tracking

unspecified
2013-06-13

Details

Attachments

(1 attachment)

215.03 KB, application/x-xpinstall
Details
(Reporter)

Description

4 years ago
Created attachment 759747 [details]
add-on

Since our push yesterday we've been getting a lot of validation timeouts (>100).  Did something change in the AMO validator?  Are timeout reasons logged somewhere?

Attached is one of the add-ons that timed out, but I can get you any others you'd like.
Duplicate of this bug: 880681
Duplicate of this bug: 880707
Seems to be the bug I fixed in https://github.com/mozilla/amo-validator/pull/203
Duplicate of this bug: 880528

Comment 5

4 years ago
I am not sure whether it is the same problem, but I get "unexpected server error happened while validating" immediately (i.e., it is not timeout). See the screencast on http://mcepl.fedorapeople.org/tmp/screencast-amo-upload.webm
(Assignee)

Updated

4 years ago
Duplicate of this bug: 880863
(Assignee)

Comment 7

4 years ago
https://github.com/mozilla/zamboni/commit/9b8b98786ffed9ec9d182e0658ec770042029f34

Leaving the bug open so that we can test that this does indeed fix the issue.
(Assignee)

Comment 8

4 years ago
Seems to be fixed now.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-06-13

Comment 9

4 years ago
For me it still gets stuck at validation as I described in https://bugzilla.mozilla.org/show_bug.cgi?id=880681

Comment 10

4 years ago
Still stuck for me as well - cannot upload a new version of FireFTP. ( https://addons.mozilla.org/en-US/firefox/addon/fireftp/ )

Comment 11

4 years ago
It's fixed in the source tree, but the fixed version hasn't been pushed to production yet.

I think there's a schedule somewhere which documents when pushes of new versions of AMO happen, but it's impossible to find. Unfortunately, this page <https://wiki.mozilla.org/AMO> is years out-of-date. It would be nice if someone on the AMO dev team would update it, or at least put a link at the top to where more current information can be found.

Comment 12

4 years ago
Hm, but I see the code to commit that Matt did is only related to Jetpack addons - my addon is not a Jetpack addon so the error I'm seeing is perhaps not fixed by that?

(Besides Matt said in comment 7 he'd leave this bug open until it was fixed) I wonder if something else is going on...
(Assignee)

Comment 13

4 years ago
You can test your add-on's submission with addons-dev.allizom.org

clouserw tentatively plans to push the fix to production on Monday.
(In reply to Mime Cuvalo from comment #12)
> Hm, but I see the code to commit that Matt did is only related to Jetpack
> addons - my addon is not a Jetpack addon so the error I'm seeing is perhaps
> not fixed by that?

Please file a separate bug and attach the XPI that fails.

Comment 15

4 years ago
Cool, thanks for your help, Matt.  Indeed it's working on allizom.org.  Strange that it's somehow my addon would be related to Jetpack validation but that's a separate question ^_^.  Thanks again!
Duplicate of this bug: 880952
Duplicate of this bug: 880978
Duplicate of this bug: 881300

Comment 19

4 years ago
I will mark it as verified since I was able to validate more add-ons on -dev.
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.