636118 - All bugs do not get updated when using Change Several Bugs at Once

Status: RESOLVED DUPLICATE of bug 636150

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[s.abraham85]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
Build Identifier: 3.6.2

When selecting a large number of Bugs to change using the Change Several Bugs at Once function, I get taken to a screen which displays the updated bugs stating that Email has been sent. My browsers throbber shows that the page download is complete but as I scroll down, I do not get to see the Bugzilla footer. 
On going back and checking the issues that were being updated, I see that only some of them actually get updated. 
Normally, I update the Version or Target Milestone and I see this happening.
If I set mail_delivery_method to None and Change several bugs, then this works correctly.

Reproducible: Sometimes

Steps to Reproduce:
1. Open a bug list page with about 30 or more issues with one or more assignees/cc
2. Click on Change Several bugs at Once
3. Select all the issues, change the version and target milestone and Save
Actual Results:  
My page refreshes and in a few seconds the browsers throbber shows that the page download is complete but as I scroll down, I do not get to see the Bugzilla footer. 
On going back and checking the issues that were being updated, I see that only some of them actually get updated.

Expected Results:  
The entire page should load and all the issues that were selected should have their version and target milestone updated.

Comment 1

[Max Kanat-Alexander]

Well, to be fair, there isn't too much we can do about this

The problem is that you're hitting a hard timeout in Apache. We send email before we send output, and if Apache doesn't get output after X seconds, it kills the process without us being able to do anything about it.

We *could* re-develop some way of sending output after *each* email sent, but that might be more complexity than it's worth.

jobqueue.pl was our solution to this problem, because it makes sending emails almost instantaneous.

My understanding is that you're running on Windows, so the ultimate solution here would be to make jobqueue.pl run on Windows.

Comment 2

[Max Kanat-Alexander]

But by the way, I do understand your problem and the frustration that it causes, and I do agree that it is a problem. But I think making jobqueue.pl work everywhere is the ultimate solution.

Comment 3

[s.abraham85]

Honestly, its not a problem for our team but an issue none the less. So not too frustrated really. For our purpose, these mass updates are best not sent to the team as they wouldn't like all the email which didn't require any action from them.
Appreciate the understanding though.

Comment 4

[Max Kanat-Alexander]

(In reply to comment #3)
> For our purpose, these mass updates are best not sent to the
> team as they wouldn't like all the email which didn't require any action from
> them.

  Yeah, for that, you probably want to see bug 26943.