Open
Description
openedon May 8, 2022
When running the bootsnap test suite on the Debian ppc64el architecture, some tests will cause bootsnap to hang forever. One can reproduce this with, for example, Bootsnap::CLITest#test_precompile_gemfile
. I can reproduce this with both ruby3.0 and ruby3.1, but only on ppc64el. No other official Debian architecture is affected.
Steps to reproduce
- Download the "ppc64el-pseries" qemu images from https://people.debian.org/~gio/dqib/.
- Unzip the contents, cd into the generated directory
- Boot the image with this command line:
qemu-system-ppc64le -machine pseries -cpu power9 -m 4G -smp 2 -drive file=image.qcow2 -device e1000,netdev=net -netdev user,id=net,hostfwd=tcp::2222-:22 -kernel kernel -initrd initrd -nographic -append "root=LABEL=rootfs console=hvc0"
- Login as root, password "root"
apt-get update && apt-get install -qy ruby-dev git
git clone https://github.com/Shopify/bootsnap.git
cd bootsnap
bundle install
bundle exec rake TESTOPTS='-v -ntest_precompile_gemfile'
(ruby3.0 is currently the default. to reproduce with ruby3,1, install ruby3.1-dev
, and use bundle3.1
instead of just bundle
in the command lines above).
the output looks like this:
# bundle exec rake TESTOPTS='-v -ntest_precompile_gemfile'
/usr/bin/gmake install target_prefix=
/usr/bin/install -c -m 0755 bootsnap.so /root/bootsnap/lib/bootsnap
cp tmp/powerpc64le-linux-gnu/bootsnap/3.0.4/bootsnap.so tmp/powerpc64le-linux-gnu/stage/lib/bootsnap/bootsnap.so
Run options: -v -ntest_precompile_gemfile --seed 52554
# Running:
Bootsnap::CLITest#test_precompile_gemfile =
(and stays there forever, until I interrupt with a control-c; but even then there are multiple processed left behind that I need to kill manually)
Bootsnap version: from git
Ruby version: 3.0 or 3.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
No labels