commitable build failed
Open
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
The very last commit to rakudo complains an executable can’t be built:
19:02 < [Coke]> c: 21dd9921d 2.put
19:02 < committable6> [Coke], ¦21dd992: «Cannot test this commit (Commit exists, but an executable could not be built
for it)»
19:03 < [Coke]> c: f6180a311 2.put
19:03 < committable6> [Coke], ¦f6180a3: «2»
One before seems fine - other CI systems don’t have a problem with 21dd9921d
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 committable6 check for commit 21dd9921d and compare it with the successful f6180a311 check. Reproduce the executable-build failure and inspect the relevant build path; done means the commit can be tested and returns executable output like the neighboring commit.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100