Raku / Raku/whateverable

Make it easier to run for contributors

Open
#122 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

whateverable
Dominant language
Raku
Stars
19
Forks
16
PR merge metrics
No merged PRs in 30d

Description

Currently you can only test some functions of Unicodable, other bots require a bunch existing rakudo revisions (which takes a few days to get done). In other words, you can only develop stuff on the server where the bots are running…

We should add some “contributor” mode for build.p6 that would only build maybe 5 revisions, and make sure that most bots are functional with just these 5 builds.

Bots that you can run and TEST locally:

  • Bisectable – OK but may fail on the first run
  • Committable – OK but may fail on the first run
  • Benchable – OK but may fail on the first run
  • Evalable – OK
  • Statisfiable
  • Unicodable – OK
  • Bloatable – requires bloaty that you have to compile yourself…
  • Quotable
  • Greppable – you have to run it twice to make it pass its tests (it pulls perl6-all-modules on the first run and times out), also seems to be too slow on my machine to get things done in time
  • Coverable – failing tests
  • Releasable
  • Nativecallable
  • Squashable – no tests yet
  • Reportable – ± no tests yet, but will run fine locally (more info on Reportable#running-the-bot-locally)
  • Notable
  • Shareable – no tests yet

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with build.p6 and inspect how the bots listed in the issue obtain and use Rakudo revisions. Run the currently marked-local bots to establish the baseline. Done means a contributor mode builds about five revisions and the remaining bots are functional and testable locally where feasible.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.