Skip to content

Test Android builds is failing with (signal: 31, SIGSYS: bad system call) #3911

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

Closed
sylvestre opened this issue Sep 8, 2022 · 3 comments · Fixed by #3915
Closed

Test Android builds is failing with (signal: 31, SIGSYS: bad system call) #3911

sylvestre opened this issue Sep 8, 2022 · 3 comments · Fixed by #3915

Comments

@sylvestre
Copy link
Contributor

dunno if it is recent regression or not


test test_cp::test_abuse_existing ... ok
test test_cp::test_canonicalize_symlink ... ok
test test_cp::test_copy_dir_symlink ... ok
error: test failed, to rerun pass '--test tests'

Caused by:
  process didn't exit successfully: `/data/data/com.termux/files/home/coreutils/target/debug/deps/tests-17fb25af23c0e087` (signal: 31, SIGSYS: bad system call)
Error: The process '/bin/sh' failed with exit code 101
Terminate Emulator

@niyaznigmatullin
Copy link
Contributor

Ran several tests, it fails at this part:

    // For debugging purposes:
    for f in me.fd().unwrap() {
        let fd = f.unwrap();
        println!("{:?} {:?}", fd, fd.mode());
    }

Here is the diff when it starts failing. Iterator::next for FDsIter fails:
niyaznigmatullin@586b391

@sylvestre
Copy link
Contributor Author

interesting. so, i regressed it, oups

I guess we could just comment this part on android

@niyaznigmatullin
Copy link
Contributor

Filed an issue, I don't understand whether this is expected: eminence/procfs#203

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants