Snap Nightly build fails with error: could not compile gkrust
Categories
(Firefox Build System :: Third Party Packaging, defect)
Tracking
(firefox-esr102 unaffected, firefox-esr115 unaffected, firefox115 unaffected, firefox116 unaffected, firefox117 unaffected, firefox118 fixed)
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | unaffected |
firefox115 | --- | unaffected |
firefox116 | --- | unaffected |
firefox117 | --- | unaffected |
firefox118 | --- | fixed |
People
(Reporter: ke5trel, Assigned: bandali)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(1 file)
Snap build error:
error: could not compile `gkrust`
Caused by:
process didn't exit successfully:
https://github.com/canonical/firefox-snap/actions/workflows/nightly-build.yml
Regression window:
https://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2023-07-15&enddate=2023-07-16
Possibly regressed by Bug 1821228.
Comment 1•1 year ago
|
||
:glandium, since you are the author of the regressor, bug 1821228, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 2•1 year ago
|
||
(signal: 9, SIGKILL: kill)
Sounds like you hit the OOM killer. IOW, not enough memory.
Comment 3•1 year ago
|
||
Considering you're building with rustc 1.66, bug 1821228 is also likely not involved.
Updated•1 year ago
|
Comment 4•1 year ago
|
||
It's broken since ~ one week but I think amin was on PTO.
Updated•1 year ago
|
Comment 5•1 year ago
|
||
[Regression triage] Hi :bandali! Based on the comments above, we currently don't think the compilation error was caused by a recent change in Firefox. Would you know if something changed around the firefox-snap repo?
Comment 6•1 year ago
|
||
(In reply to Johan Lorenzo [:jlorenzo] from comment #5)
[Regression triage] Hi :bandali! Based on the comments above, we currently don't think the compilation error was caused by a recent change in Firefox. Would you know if something changed around the firefox-snap repo?
Johan, this is an OOM situation it has happened several times and it's due to GitHub Actions limitations
Comment 7•1 year ago
|
||
The bug is marked as tracked for firefox117 (nightly). We have limited time to fix this, the soft freeze is in a day. However, the bug still isn't assigned.
:gcp, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Updated•1 year ago
|
[Tracking Requested - why for this release]:
Candidate and beta snap channels haven't seen any new updates since 2023-07-21 so it appears this is blocking 116 release.
Updated•1 year ago
|
Comment 9•1 year ago
|
||
fwiw i dont think this is blocking the 116 release(atleast not anymore) since I see 116.0-2 builds in snap.
Reporter | ||
Comment 10•1 year ago
|
||
All channels have receive updates except the edge channel which is still blocked.
Assignee | ||
Comment 11•1 year ago
|
||
Hi all,
Apologies for the slow reply here, partly because I was indeed on PTO earlier. I was in touch with some Mozilla folks after my return last week, and indeed, the Stable, Beta, and ESR build failures were due to a Launchpad issue that has since been resolved, and as you noticed the snap builds for these have been available and ready to go.
The only one currently missing is Nightly (edge), which has been broken from what I can tell because the GitHub-provided runners for GitHub Actions (used for Nightly snap builds) are too small (and we had sporadic issues with them earlier too). I've been working on clearing a path forward for this, using self-hosted runners, and I hope to have more news on this front soon.
Assignee | ||
Comment 12•1 year ago
|
||
Hi again,
I ended up moving the Nightly snap build over to Launchpad, like the other Firefox snap series. I believe this can be marked as resolved once the needed changes for collecting the debug symbols for Nightly are made (I opened a PR but I'm not sure if anything else may be needed to close the gap).
Assignee | ||
Comment 13•1 year ago
|
||
Comment 14•1 year ago
|
||
Comment 15•1 year ago
|
||
bugherder |
Updated•1 year ago
|
Description
•