Redox CI failure
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 1.3k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 69
Description
...
warning: libc-test@0.1.0: detected versions: Versions { linux: None, glibc: None, freebsd: None, openbsd: None, netbsd: None, macos: None, emscripten: None, wasi_sdk: None, android: None }
warning: libc-test@0.1.0: /checkout/target/x86_64-unknown-redox/debug/build/libc-test-c248624186d593e8/out/ctest_output.c:98:8: error: unknown type name 'sighandler_t'
warning: libc-test@0.1.0: 98 | static sighandler_t ctest_const_SIG_DFL_val_static = SIG_DFL;
warning: libc-test@0.1.0: | ^~~~~~~~~~~~
warning: libc-test@0.1.0: /checkout/target/x86_64-unknown-redox/debug/build/libc-test-c248624186d593e8/out/ctest_output.c:98:54: error: initialization of 'int' from 'void (*)(int)' makes integer from pointer without a cast [-Werror=int-conversion]
...
cc: @willnode
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing or inspecting the Redox CI failure in the libc-test build, focusing on the generated ctest_output.c location shown in the log and the unknown sighandler_t error. Trace how the libc-test bindings are generated for Redox, then verify the fix by rerunning the affected Redox CI check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- ci-cd, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100