bad build
Open
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
21:55 < [Coke]> c: af3df50dba e.say
21:55 < committable6> [Coke], ¦af3df50: «Cannot test this commit (Commit exists, but an executable could not be built
for it)»
21:56 < Geth> ¦ whateverable/main: 19b6d735ed | (Will Coleda)++ | .ping
21:56 < Geth> ¦ whateverable/main: WIP
21:56 < Geth> ¦ whateverable/main: review: https://github.com/Raku/whateverable/commit/19b6d735ed
22:03 < [Coke]> c: af3df50dba e.say
HEAD not built, pinged the repo to restart the bots... didn't reconnect.
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 checking the bot and build output for commit af3df50dba, then review the reported attempt to restart the bots. Done means the HEAD commit produces an executable and the bots reconnect and process a test request.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100