compiler/runtimeIssues related to the Go compiler and/or runtime.NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.
The revived linux-amd64-alpine builder has flaked twice in its short new lifetime with 'unexpected return pc' crashes during the cgo tests.
Here is a repro case using a gomote (note that if you ssh in, you have to set up your environment manually, and in particular you have to put /workdir/go/bin at the front of PATH and have to set GOROOT_BOOTSTRAP=/workdir/go1.4). Not sure why the environment is so messed up on Alpine. gomote run does not have these problems, only gomote ssh.
VM=$(gomote create linux-amd64-alpine)
gomote push $VM
gomote run $VM go/src/make.bash
gomote put -mode 0777 $VM - try.sh <<'EOF'
#!/bin/bash
cd /workdir/go/misc/cgo/test
for i in $(seq 100); do
date
if ! /workdir/go/bin/go test >log 2>&1; then
cat log
fi
done
EOF
gomote run $VM try.sh
You may need to repeat the try.sh a few times depending on how flaky the machine is feeling but most runs get at least one failure.
compiler/runtimeIssues related to the Go compiler and/or runtime.NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.
3 participants
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.
The revived linux-amd64-alpine builder has flaked twice in its short new lifetime with 'unexpected return pc' crashes during the cgo tests.
Here is a repro case using a gomote (note that if you ssh in, you have to set up your environment manually, and in particular you have to put /workdir/go/bin at the front of PATH and have to set GOROOT_BOOTSTRAP=/workdir/go1.4). Not sure why the environment is so messed up on Alpine. gomote run does not have these problems, only gomote ssh.
You may need to repeat the try.sh a few times depending on how flaky the machine is feeling but most runs get at least one failure.
Here are some failures from that script:
This one did not happen during garbage collection:
Here are the two build dashboard failures:
https://build.golang.org/log/658036e08c7a1d218c33808fdd1d6612b40502d8
and
https://build.golang.org/log/94cf14d78b116487dc76a921baf6ba76480a4c7a
Perhaps this is Alpine-specific, or perhaps it is musl-related.
The Alpine image may have an old Linux kernel; maybe we should update it.
There are a few other open 'unexpected return pc' issues.
Maybe they are all stale:
#35005 is the most interesting one but the repro case is a very large program running under Docker.
The text was updated successfully, but these errors were encountered: