test/recallpassagecheck.sh and test/impactpartitioncheck.sh are committed 100644 — direct invocation exits 126
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bash, shell
- Domain
- testing-qa
Research direction
Start with test/recallpassagecheck.sh and test/impactpartitioncheck.sh, comparing their tracked modes with the other test/*check.sh scripts. Inspect test/manifestcheck.sh for the existing suite enumeration, then verify that direct invocation works and the manifest prevents executable-mode regressions.
Written by the indexing model from the issue text.
Description
Part of #342.
Version: 3fcd515f (mode recorded in the git index)
$ git ls-files -s test/recallpassagecheck.sh test/impactpartitioncheck.sh
100644 1cac65e2… test/recallpassagecheck.sh
100644 … test/impactpartitioncheck.sh
Every other test/*check.sh is 100755. Invoked the way the rest of the suite is invoked —
./test/recallpassagecheck.sh # /bin/bash: ./test/recallpassagecheck.sh: Permission denied (exit 126)
./test/impactpartitioncheck.sh # exit 126
test/regression.sh and test/pargates.py call them through a shell, so CI never notices; contributors and
any tooling that execs the suite directly get a silent 126. Both scripts pass when run as
bash test/<gate>.sh (impactpartitioncheck fully green; recallpassagecheck green once the clone has full
history, which it checks and explains itself).
Fix
git update-index --chmod=+x (or chmod +x + commit) both files. A manifest arm could pin "every
test/*check.sh is 100755" so the mode cannot regress — test/manifestcheck.sh already enumerates the suite.
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 145
- Avg merge
- 8h 50m
- Merged PRs (30d)
- 211
Getting set up
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.
More from redhat-et/ripwire
-
Difficulty 2/5 Under an hour Newbie friendliness 78/100
redhat-et/ripwire#334 · 7 comments ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
redhat-et/ripwire#68 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
One shared inert-region mechanism (quote, discard, comment forms) instead of per-language checksOpenenhancement help wanted
Difficulty 3/5 Half a day Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
All issues in redhat-et/ripwire
Similar issues
-
Unconfirmed bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
luanti-org/luanti#17605 · 1 comment ·
Maintainers usually reply within 2 days
-
area: config area: firmware priority: P2 - medium size: S type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Mizithra/ActiveTerrain#16 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
grumpycoders/pcsx-redux#2171 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
bytedance/trae-agent#524 · 1 comment ·
Maintainers usually reply within 1 day