CI fails if test file contains the word "unexpected" or "unresolved"
Open
Nobody has claimed this yet.
bug
CI
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 231
- Avg merge
- 19h 55m
- Merged PRs (30d)
- 67
Description
https://github.com/Rust-GCC/gccrs/pull/2373 is failing because @MahadMuhammad added a testfile named "unexpected_arguments.rs". This is a funny behavior but it would be nice not to have it haha.
https://github.com/Rust-GCC/gccrs/actions/runs/5465722215/jobs/9949574002?pr=2373
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 GitHub Actions run linked in the issue and the test file named unexpected_arguments.rs, then trace the CI entry point that handles test filenames containing "unexpected" or "unresolved". Done means such filenames no longer make the workflow fail and the affected CI job passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, github-actions, rust
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100