Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x86_64-linux-gnummtk build is broken #57306

Closed
inkydragon opened this issue Feb 7, 2025 · 0 comments · Fixed by #57298
Closed

x86_64-linux-gnummtk build is broken #57306

inkydragon opened this issue Feb 7, 2025 · 0 comments · Fixed by #57298
Labels
building Build system, or building Julia or its dependencies ci Continuous integration GC: MMTK MMTK GC integration

Comments

@inkydragon
Copy link
Member

After #57253

[11485] signal 11 (1): Segmentation fault
in expression starting at abstractarray.jl:1246
Allocations: 0 (Pool: 0; Big: 0); GC: 0
Segmentation fault
make[1]: *** [sysimage.mk:69: [buildroot]/usr/lib/julia/basecompiler.ji] Error 139

https://buildkite.com/julialang/julia-master/builds/44448#0194daf8-2cad-4bf8-bb40-7c26dde2195d/824-2439

@inkydragon inkydragon added building Build system, or building Julia or its dependencies ci Continuous integration GC: MMTK MMTK GC integration labels Feb 7, 2025
@d-netto d-netto closed this as completed in 72f8a10 Feb 8, 2025
KristofferC pushed a commit that referenced this issue Feb 11, 2025
Updating mmtk-julia version to include
mmtk/mmtk-julia#228 and fix the MMTk CI.

I've also changed the allocation profiler tests to skip all tests
instead of just a few since I've seen some spurious errors - they should
all be related though, we need to make sure the profiler accounts for
fastpath allocation (see
#57103)

This should fix #57306.

(cherry picked from commit 72f8a10)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
building Build system, or building Julia or its dependencies ci Continuous integration GC: MMTK MMTK GC integration
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant