-
Notifications
You must be signed in to change notification settings - Fork 18k
syscall: TestDeathSignal failed in github code space. #62719
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
Comments
This is one of the tests that was also failing on the LUCI builders, and was skipped there in https://go.dev/cl/513779 (CC @dmitshur @heschi). As I commented on that CL:
@qiulaidongfeng, want to send a CL implementing that approach? |
Yes, I will send the CL after repairing the test failure according to your method.
…---Original---
From: "Bryan C. ***@***.***>
Date: Tue, Sep 19, 2023 22:09 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [golang/go] syscall: TestDeathSignal failed in github code space.(Issue #62719)
This is one of the tests that was also failing on the LUCI builders and was skipped in https://go.dev/cl/513779 (CC @dmitshur @heschi).
As I commented on that CL:
I suspect that the real problem in this case is that the deathSignalParent function hard-codes a specific UID and GID that probably don't apply in a chroot:
https://cs.opensource.google/go/go/+/master:src/syscall/exec_pdeathsig_test.go;l=111-113;drc=2ad666dea0490305bb7fd2dd6e7beb767acfd2c3
Probably the test should be changed to look up the actual UID and GID for nobody, and should skip the test if that lookup fails.
@qiulaidongfeng, want to send a CL implementing that approach?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Fixes golang#62719 Change-Id: I3fe2fde919f588fa553a2f849cd7b35cf7a5efbd
Fixes golang#62719 Change-Id: I3fe2fde919f588fa553a2f849cd7b35cf7a5efbd
Fixes golang#62719 Change-Id: I3fe2fde919f588fa553a2f849cd7b35cf7a5efbd
Fixes golang#62719 Change-Id: I3fe2fde919f588fa553a2f849cd7b35cf7a5efbd
Fixes golang#62719 Change-Id: I3fe2fde919f588fa553a2f849cd7b35cf7a5efbd
Change https://go.dev/cl/529735 mentions this issue: |
Change https://go.dev/cl/529795 mentions this issue: |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Fork golang/go in github, see https://docs.github.com/en/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository Create a code space.
See also https://docs.github.com/en/codespaces/developing-in-codespaces/opening-an-existing-codespace Open the code space.
cd src
./all.bash
What did you expect to see?
Test passed.
What did you see instead?
death signal parent error: fork/exec /tmp/TestDeathSignal3458263251/syscall.test: permission denied
--- FAIL: TestDeathSignal (0.00s)
exec_pdeathsig_test.go:97: did not receive start from child, received "", EOF
FAIL
FAIL syscall 1.447s
The text was updated successfully, but these errors were encountered: