properly block ppc users from getting 3.5, 3.6 MU requests



Release Engineering
7 years ago
5 years ago


(Reporter: bhearsum, Assigned: bhearsum)


Firefox Tracking Flags

(Not tracked)




7 years ago
Apparently we didn't do this properly, #planning reports PPC users getting offered updates, and ending up with a broken browser.

[15:28] <tracy> biggest issue of concern I am seeing at sumo is mac ppc users getting stranded.  
[15:28] --> sfink has joined this channel (
[15:28] <tracy> was it not possible to turn off upgrade for that OS?
[15:29] <khuey> beltzner: ^^
[15:31] <bsmedberg> tracy: we did! no?
[15:32] <tracy> people are reporting "upgrade" to 4.0 from 3.6.x and are stuck with a broken browser.
[15:32] <bhearsum> uh, really?!
[15:32] <catlee> are they getting upgrading to a broken browser?
[15:32] * bhearsum looks
[15:32] <tracy> I fgure if they knew download 4 then they'd knwo to download 3.6 to get back.
[15:33] <aja> catlee: 4.0 is no good for ppc / os x 10.4


7 years ago
Assignee: nobody → bhearsum
Priority: -- → P1
OS: Linux → Mac OS X
Hardware: x86_64 → PowerPC

Comment 1

7 years ago
Turns out we accidentally pushed snippets for PPC users of 3.5.17 and 3.6.15. I've deleted them now, and Tracy is verifying everything.

The 3.5.18 and 3.6.16 MUs are not affected by this.

Comment 2

7 years ago
Tracy just verified that we're now in a state where:
- PPC users are not getting offered MUs
- i386/x86_64 users are.

Very very very sorry for these snippets getting pushed in the first place, this is all fixed now.
Last Resolved: 7 years ago
Resolution: --- → FIXED
Preserving details for the curious: 

Before 3.5.18/3.6.16, RelEng would generate all updates and then manually removed the PPC snippets. Update code was fixed to special-case PPC after 3.5.17/3.6.15 and before 3.5.18/3.6.16.  
RelEng has this manually correct for 3.5.17/3.6.15 -> FF4.0rc1
RelEng missed manually fixing this when doing 3.5.17/3.6.15 -> 4.0rc2
RelEng has this automatically correct for 3.5.18/3.6.16 -> FF4.0rc2

RelEng have no automated tests for this and not clear we can easily automate tests for this.

After 3.5.17/3.6.15, the code for MU snippets branched for 4.0; 3.5, 3.6
* branch1 does update ppc for 3.5->3.5, 3.5->3.6, 3.6->3.6
** 3.5.17->4.0, 3.6.15->4.0 was here
** branch2 (new)) does not update ppc for 3.5/3.6 -> 4.0
* 3.5.18->4.0, 3.6.16->4.0 was here
** branch does not update ppc for 4.0->4.0
(In reply to comment #3)
> RelEng have no automated tests for this and not clear we can easily automate
> tests for this.

Al, looks like we should add this to our testing matrix?
Isn't this a one-time deal rather than something needed for ongoing tests?

Comment 6

7 years ago
We should always check that PPC is a negative case for update tests on 4
Product: → Release Engineering
You need to log in before you can comment on or make changes to this bug.