Closed Bug 648225 Opened 11 years ago Closed 10 years ago
Performance of platform-dependent add-ons is not tested
Talos currently uses URLs like https://addons.mozilla.org/en-US/firefox/downloads/latest/5579 to download add-ons. This URL (which belongs to Cooliris by the way) will not work however because it is a platform-dependent add-on with different downloads for different platforms. Consequently the performance of the add-on will simply not be tested. Instead the AMO API should be used - https://services.addons.mozilla.org/en-US/firefox/api/1/addon/5579 contains all the download links for the supported platforms.
If there are platform specific versions of addons we should definitely be testing the correct addon per platform. I'm going to need to investigate how to change our download/install system to get this up and running. Is the only route to win here reading that xml file?
Assignee: nobody → anodelman
(In reply to comment #1) > Is the only route to win here reading that xml file? You can fall back to platform-specific URLs, like https://addons.mozilla.org/firefox/downloads/latest/5579/platform:3/addon-5579-latest.xpi (platform=3 is Mac OS) However, the "latest" URL only works for add-ons with Public status, so this is also going to fail for other cases.
From the look of it, https://addons.mozilla.org/firefox/downloads/latest/1419/platform:5/ will always work - even for add-ons that are not platform-specific. platform:5 is Windows, Linux is 2, OS X is 3. No idea what the other codes stand for.
This addon given as an example: https://services.addons.mozilla.org/en-US/firefox/api/1/addon/5579 appears to only have winnt and darwin versions - should we not test it on linux if the addon does not provide a platform specific link?
We shouldn't test on platforms the add-on doesn't claim to support.
https://addons.mozilla.org/firefox/downloads/latest/5579/platform:2/ results in 404 - so the test on Linux will fail "automatically".
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.