848700 - Mass changing bugs times out after 60s, no easy way to resume

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: General, defect)

Description

[Ed Morley [:emorley]]

1) Go to https://bugzilla.mozilla.org/buglist.cgi?chfieldto=-3m&field0-0-0=status_whiteboard&field0-1-0=status_whiteboard&keywords=intermittent-failure&keywords_type=allwords&query_format=advanced&resolution=---&type0-0-0=nowordssubstr&type0-1-0=notsubstring&value0-0-0=random%20disabled%20marked%20fuzzy%20todo%20fails%20failing%20annotated%20time-bomb&value0-1-0=leave%20open&order=changeddate%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id&tweak=1
(roughly 320 bugs shown for me right now)
2) Use "check all bugs"
3) Adjust settings to set status to "resolved WFM" and add a comment
4) Press submit

Expected:
Mass change takes a while, but doesn't time out.

Actual:
Mass change times out after 60 seconds after only changing 20-30 of the 300+ bugs. To continue with the next batch of 20-30, I have to start all over again :-(

Note: I don't mind it taking ages, I just want to not have to do 10-15 batches.

Comment 1

[Ed Morley [:emorley]]

In fact, many times it's only changing 5-10 bugs before timing out :-(

Comment 2

[Dietrich Ayala (:dietrich)]

This is really problematic, and blocking B2G drivers' ability to get work done.

Comment 3

[:glob ✱]

what is the exact message you get when it times out?
are you able to provide an exact time when you receive an error?

Comment 4

[Dietrich Ayala (:dietrich)]

No message. It's just a blank white page.

Hm, no, but should be easy for someone to reproduce.

Comment 5

[:glob ✱]

:ashish discovered that the socket timeout on the load-balancer was set to 40 seconds (the old load-balancer had it set to 300s).  it's been adjusted, please let me know if this makes any difference.

Comment 6

[Ed Morley [:emorley]]

(In reply to Dietrich Ayala (:dietrich) from comment #4)
> No message. It's just a blank white page.

Same for mine (comment 0)

Comment 7

[:glob ✱]

as i'm pretty sure the issue was the load-balancer timeout, i'm going to call this fixed.