Closed
Bug 756532
Opened 12 years ago
Closed 12 years ago
Clobberer fails to work if you try to clobber more than 1024 things at once, like all of mozilla-inbound
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: jhopkins)
References
Details
Attachments
(1 file)
7.87 KB,
patch
|
jhopkins
:
review+
jhopkins
:
checked-in+
|
Details | Diff | Splinter Review |
Using either: https://build.mozilla.org/clobberer/?branch=mozilla-central or https://build.mozilla.org/clobberer/?branch=mozilla-inbound If you try to clobber everything at once (the master check box in the left hand column) and submit the form; the clobberer page that is returned, shows a blank "last clobbered" column, rather than the current date/time and LDAP login used. Presumably due to the POST data exceeding a certain size.
Reporter | ||
Comment 1•12 years ago
|
||
Sorry, intended to add: Works fine if you only check a subset of the boxes on each submit.
Comment 2•12 years ago
|
||
heh, not sure why I'm copied here -- I'm definitely not the one who will be rewriting clobberer to be smarter :)
Comment 3•12 years ago
|
||
Oh, failed to actually type the comment which went with the cc, which was suspicion that it was something in front of clobberer in its new home, which thinks that n bytes of postdata is fine, but m bytes is an attack that must be thwarted.
Comment 4•12 years ago
|
||
Comment 0 misleadingly does cast the blame on clobberer itself, talking about returning a blank last clobbered column, when in fact that was just what the tree we were clobbering at the time had. The actual "Actual Result" is that the return from the post is exactly what the page looked like before, just like you didn't send a thing.
Reporter | ||
Comment 5•12 years ago
|
||
Sorry, I should have made that more explicit.
Comment 7•12 years ago
|
||
Hm, yes - but I thought clobberer used POST? Could we change it to POST instead?
Comment 8•12 years ago
|
||
It does POST - I wasn't worried about GET URL length so much as the multiple layers of things limiting total request size, starting with PHP's post_max_size out through Apache's LimitRequestBody and all the firewalls and load balancers in front of Apache that might also limit request size.
Comment 9•12 years ago
|
||
I don't see any such settings in Zeus. Jake, is there such a thing?
Comment 10•12 years ago
|
||
I'm not aware of any such setting in Zeus. It might be possible to do something like this in a Service Protection Class (I don't know), but there are none enabled for the virtual servers handling this domain (build.mozilla.org). How big is the incoming POST data? post_max_size = 8M LimitRequestBody is unset, so it should default to 0 (unlimited)
Comment 11•12 years ago
|
||
Sigh. It's tiny, just a pair of "slave-100125: on" for each builder listed, so I was going to estimate how big it was by counting the rows. That would be (currently, not at the time this was filed, because things get pruned out) 761 pairs for mozilla-central, which currently doesn't hit this (sorry, we'll be having clobbered builds all day), and in a very obvious pointer to the nature of the problem in clobberer's PHP somewhere, 1031 pairs for mozilla-inbound, which still hits this.
Summary: Clobberer fails to work if you try to clobber everything at once (mozilla-central & inbound) → Clobberer fails to work if you try to clobber more than 1024 things at once, like all of mozilla-inbound
Comment 12•12 years ago
|
||
Smells like running out of parameters in the mysql query to me.
Reporter | ||
Comment 13•12 years ago
|
||
Is there anyone who can drive this forwards? This is impacting me (and others) pretty often.
Reporter | ||
Comment 14•12 years ago
|
||
Ping? Something like bug 614262 would also fix this.
Reporter | ||
Updated•12 years ago
|
Severity: major → blocker
Updated•12 years ago
|
Assignee: nobody → armenzg
Comment 15•12 years ago
|
||
Setting to "major" as it does not "block" any trees or releases. I have no idea about clobberer so I will do my best to figure this out.
Severity: blocker → major
Assignee | ||
Comment 17•12 years ago
|
||
Test URL: https://build.mozilla.org/stage-clobberer/index-test.php
Assignee | ||
Updated•12 years ago
|
Attachment #637546 -
Flags: review?(catlee)
Reporter | ||
Comment 18•12 years ago
|
||
<3 jhopkins :-D
Assignee | ||
Comment 19•12 years ago
|
||
Comment on attachment 637546 [details] [diff] [review] proposed patch armenzg r+'d via IRC
Attachment #637546 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 20•12 years ago
|
||
Comment on attachment 637546 [details] [diff] [review] proposed patch Landed in http://hg.mozilla.org/build/tools/rev/c80a6efb18bb and deployed to production.
Attachment #637546 -
Flags: checked-in+
Assignee | ||
Comment 21•12 years ago
|
||
mozilla-inbound clobbered ok.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 22•12 years ago
|
||
Thank you :-D
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•