>I see. Are those per-commit builds exposed anywhere? I can just try downloading them manually... Yeah, but believe me that's going to be a big nuisance since you'd have to chase them down throughout our CI. >I'm trying not to install too much random junk on the work VM. At least Firefox is approved, and I justify nightlies for advance testing of browser changes. mozregression is available as a commandline python script on PIP, if that helps. It will unpack into a tempdir so it's not installing anything. >Also, can you get me the changeset for the morning of the 10th, the one I can't access? The one the Windows x64 would have been built off of. I guess for starters I could eyeball that range for anything suspicious. Say, webrender "hm, what happens if I turn off webrender" that kinda thing. See above. I'm worried about bug 1768014 because it moves around things in process startup and returns and error if things go wrong (instead of crashing, which would leave a trace). So, if mozregression can't be used, perhaps you can try: 292df8ed886d https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/W1zTxeCIT8SHQBZZsgJBcQ/runs/0/artifacts/public/build/install/sea/target.installer.exe https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/W1zTxeCIT8SHQBZZsgJBcQ/runs/0/artifacts/public/build/target.zip 53032d712512 https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GtZrIMQ0T52FW55gfPcrmQ/runs/0/artifacts/public/build/install/sea/target.installer.exe https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GtZrIMQ0T52FW55gfPcrmQ/runs/0/artifacts/public/build/target.zip And check which of these builds work, or is broken, or both work or are broken.
Bug 1769845 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
>I see. Are those per-commit builds exposed anywhere? I can just try downloading them manually... Yeah, but believe me that's going to be a big nuisance since you'd have to chase them down throughout our CI. >I'm trying not to install too much random junk on the work VM. At least Firefox is approved, and I justify nightlies for advance testing of browser changes. mozregression is available as a commandline python script on PIP, if that helps. It will unpack the Firefoxes into a tempdir so it's not installing anything. >Also, can you get me the changeset for the morning of the 10th, the one I can't access? The one the Windows x64 would have been built off of. I guess for starters I could eyeball that range for anything suspicious. Say, webrender "hm, what happens if I turn off webrender" that kinda thing. See above. I'm worried about bug 1768014 because it moves around things in process startup and returns an error if things go wrong (instead of crashing, which would leave a trace). So, if mozregression can't be used, perhaps you can try: 292df8ed886d https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/W1zTxeCIT8SHQBZZsgJBcQ/runs/0/artifacts/public/build/install/sea/target.installer.exe https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/W1zTxeCIT8SHQBZZsgJBcQ/runs/0/artifacts/public/build/target.zip 53032d712512 https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GtZrIMQ0T52FW55gfPcrmQ/runs/0/artifacts/public/build/install/sea/target.installer.exe https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GtZrIMQ0T52FW55gfPcrmQ/runs/0/artifacts/public/build/target.zip And check which of these builds work, or is broken, or both work or are broken.
>I see. Are those per-commit builds exposed anywhere? I can just try downloading them manually... Yeah, but believe me that's going to be a big nuisance since you'd have to chase them down throughout our CI. >I'm trying not to install too much random junk on the work VM. At least Firefox is approved, and I justify nightlies for advance testing of browser changes. mozregression is available as a commandline python script on PIP, if that helps. It will unpack the Firefoxes into a tempdir so it's not installing anything. >Also, can you get me the changeset for the morning of the 10th, the one I can't access? The one the Windows x64 would have been built off of. I guess for starters I could eyeball that range for anything suspicious. Say, webrender "hm, what happens if I turn off webrender" that kinda thing. See above. I'm worried about bug 1768014 because it moves around things in process startup and returns an error if things go wrong (instead of crashing, which would leave a trace). So, if mozregression can't be used, perhaps you can try: 292df8ed886d https://archive.mozilla.org/pub/firefox/nightly/2022/05/2022-05-09-09-47-10-mozilla-central/ https://archive.mozilla.org/pub/firefox/nightly/2022/05/2022-05-09-09-47-10-mozilla-central/firefox-102.0a1.en-US.win64.installer.exe 53032d712512 https://archive.mozilla.org/pub/firefox/nightly/2022/05/2022-05-10-09-55-38-mozilla-central/ https://archive.mozilla.org/pub/firefox/nightly/2022/05/2022-05-10-09-55-38-mozilla-central/firefox-102.0a1.en-US.win64.installer.exe And check which of these builds work, or is broken, or both work or are broken.
>I see. Are those per-commit builds exposed anywhere? I can just try downloading them manually... Yeah, but believe me that's going to be a big nuisance since you'd have to chase them down throughout our CI. >I'm trying not to install too much random junk on the work VM. At least Firefox is approved, and I justify nightlies for advance testing of browser changes. mozregression is available as a commandline python script on PIP, if that helps. It will unpack the Firefoxes into a tempdir so it's not installing anything. >Also, can you get me the changeset for the morning of the 10th, the one I can't access? The one the Windows x64 would have been built off of. I guess for starters I could eyeball that range for anything suspicious. Say, webrender "hm, what happens if I turn off webrender" that kinda thing. See above. I'm worried about bug 1768014 because it moves around things in process startup and returns an error if things go wrong (instead of crashing, which would leave a trace). So, if mozregression can't be used, perhaps you can try: 292df8ed886d <oops> 53032d712512 <oops> And check which of these builds work, or is broken, or both work or are broken.
>I see. Are those per-commit builds exposed anywhere? I can just try downloading them manually... Yeah, but believe me that's going to be a big nuisance since you'd have to chase them down throughout our CI. >I'm trying not to install too much random junk on the work VM. At least Firefox is approved, and I justify nightlies for advance testing of browser changes. mozregression is available as a commandline python script on PIP, if that helps. It will unpack the Firefoxes into a tempdir so it's not installing anything. >Also, can you get me the changeset for the morning of the 10th, the one I can't access? The one the Windows x64 would have been built off of. I guess for starters I could eyeball that range for anything suspicious. Say, webrender "hm, what happens if I turn off webrender" that kinda thing. See above. I'm worried about bug 1768014 because it moves around things in process startup and returns an error if things go wrong (instead of crashing, which would leave a trace). So, if mozregression can't be used, perhaps you can try: 292df8ed886d https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/W1zTxeCIT8SHQBZZsgJBcQ/runs/0/artifacts/public/build/install/sea/target.installer.exe https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/W1zTxeCIT8SHQBZZsgJBcQ/runs/0/artifacts/public/build/target.zip 53032d712512 https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GtZrIMQ0T52FW55gfPcrmQ/runs/0/artifacts/public/build/install/sea/target.installer.exe https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GtZrIMQ0T52FW55gfPcrmQ/runs/0/artifacts/public/build/target.zip And check which of these builds work, or is broken, or both work or are broken.