Run all workspace tests in CI (Windows)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
Similar to #7392, it would be nice to run all tests in CI, on MacOS (basically adding workspace-tests: true to some windows jobs in the matrix).
When I tried in #7386, I hit this issue:
error: failed to run custom build command for `uu_stdbuf_libstdbuf v0.0.29 (D:\a\coreutils\coreutils\src\uu\stdbuf\src\libstdbuf)`
...
src/libstdbuf.rs(18): error C2065: 'constructor': undeclared identifier
src/libstdbuf.rs(18): error C2182: '__attribute': this use of 'void' is not valid
src/libstdbuf.rs(19): error C2146: syntax error: missing ';' before identifier '__stdbuf_init'
src/libstdbuf.rs(19): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
src/libstdbuf.rs(21): warning C4508: '__stdbuf_init': function should return a value; 'void' return type assumed
I think libstdbuf.rs should simply not be built on Windows platform -- AFAICT nothing that is supported on Windows uses it.
Of course, there might be some more issues after this.
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 with the CI job matrix changes discussed in #7392 and the failed attempt in #7386. Inspect src/uu/stdbuf/src/libstdbuf.rs and the Windows build output to determine how it should be excluded, then run the affected workspace CI tests to confirm all Windows jobs pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100