Nightly ASAN Linux builds not getting updated
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: diegocg, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
I download the nightly Linux ASAN build every day, but since a few days the build ID isn't updated, which I guess it means that the builds are not getting updated.
Actual results:
Steps:
1: Download https://index.taskcluster.net/v1/task/gecko.v2.mozilla-central.latest.firefox.linux64-asan-opt/artifacts/public/build/target.tar.bz2 (the URL indicated in the wiki)
2. Uncompress it and run Firefox
3. Check build id in about:support. It's 20191109093718. Help -> About says I'm running 72.0a1 (2019-11-09) (64-bit). Updater tries to update to a new version.
Expected results:
I should be getting the latest version.
Comment 2•5 years ago
|
||
Hm, this might be related to the Taskcluster split. The links in MDN need updating, setting a needinfo for myself for that. But I don't know exactly why that should cause the updater to fail (my own instance updated properly).
Comment 3•5 years ago
|
||
I've updated the links in the wiki to point to Firefox-CI.
Thanks!
I have noticed that the build with the links you provided has no asanreporter.apiurl preference. Is this to be expected?
Never mind, by mistake I downloaded the build from the link in https://developer.mozilla.org/en-US/docs/Mozilla/Testing/Firefox_and_Address_Sanitizer, instead of the one in https://developer.mozilla.org/en-US/docs/Mozilla/Testing/ASan_Nightly_Project
Comment 6•5 years ago
|
||
Yes, the link in your first comment is to the regular mozilla-central builds that don't support updates. These must be updated manually. (wiki https://developer.mozilla.org/en-US/docs/Mozilla/Testing/Firefox_and_Address_Sanitizer).
The builds here: https://developer.mozilla.org/en-US/docs/Mozilla/Testing/ASan_Nightly_Project do support automatic updates, and have the asanreporter.apiurl
pref as expected.
Comment 7•5 years ago
|
||
Hi,
Due to the fact that the issue is no longer reproducible I will close this bug as Resolved - Worksforme. If anyone can still reproduce the issue please feel free to reopen the bug.
Thanks.
Description
•