Closed Bug 967655 Opened 10 years ago Closed 10 years ago

Mac OSX 10.6, upgrades from 24.2.0esr have wrong update URL

Categories

(Firefox :: General, defect)

24 Branch
x86
macOS
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: mwobensmith, Unassigned)

References

(Depends on 1 open bug)

Details

Update test automation shows that attempts to update from 24.2.0 to 24.3.0 ESR are failing on 10.6 only.

The update URL appears to be pointing to the wrong branch.

Report:
http://mozmill-daily.blargon7.com/#/update/report/0906e2c8b6f223d6588987bcd1965715

The update URL is pointing here, but this is not 24.3.0esr:
https://aus3.mozilla.org/update/3/Firefox/27.0/20140127194636/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/releasetest/Darwin%2010.8.0/default/default/update.xml?force=1
Why Firefox 29.0a1 tries to use esr24-nightly channel?
this one is very strange.  here is the update snippet from the above report.  https://aus4.mozilla.org/update/3/Firefox/29.0a1/20140201030204/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/nightly-esr24/Darwin%2010.8.0/default/default/update.xml?force=1  

<updates>
<update type="minor" version="24.3.0esrpre" extensionVersion="24.3.0esrpre" buildID="20140204000503">
<patch type="complete" URL="http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014/02/2014-02-04-00-05-03-mozilla-esr24/firefox-24.3.0esrpre.en-US.mac.complete.mar" hashFunction="sha512" hashValue="a31b90f8192dadeeac92c45d8c379d6f5da4a368a8a85d30af56bf86601bbbf0065e86b221383c8c9e363dfeea7f051ada740c1b43dab62d54b88f07189f01fb" size="55110386"/>
</update>
</updates>

wires are crossed somewhere.
Why is the 29.0a1 build on the nightly-esr24 branch?
It's test machine corruption.  This is probably invalid.  but will let matt mark it so once he's comfortable with whimboos investigation on the mozmill test farm.
Note: the installer doesn't have any part in providing the application's update url so moving to general. Note: toolkit -> app update doesn't either.
Component: Installer → General
This has turned out to be an issue with our automated test machine. Not a real Firefox bug. 

Closing now.

https://github.com/mozilla/mozmill-automation/issues/90#issuecomment-27196056
Finally closing...
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Actually the underlying problem for this weird behavior is a bug in mozinstall. We will get this fixed via bug 969334. For now the affected machine has been restored and is running properly again.
You need to log in before you can comment on or make changes to this bug.