Make it easier to run for contributors #122
Comments
AlexDaniel
added
the
whateverable
This way git wouldn't want you to commit it by default. Related issue: #122
Previously if you wanted to run bisectable or some other bot locally you had to build tens (if not thousands) of rakudo versions to get something useful out of it. Now whenever it stumbles upon a missing build it will attempt to pull it from the main server. If you're on linux x86_64, this means that the bots you start are no worse than the ones running on the main server. Note, however, that this does not let you *use* these bots as tools locally. Well, unless you fire up your own IRC server and configure the thing to use it. We will get this working next, for now this is a huge step already (see #122). Ah, almost forgot to mention, this does not work. See rakudo/rakudo#1501. I mean, yeah, you can probably use committable, evalable and some other bots, but bisectable will run out of memory before you get to any useful result.
|
Actually, almost every bot is now almost 100% usable on linux x86_64 (it will pull builds from the server and you don't have to wait for anything). That's pretty cool, and someone just has to confirm that every bot is indeed usable. Alternatively we can try running through the test suite locally, but that would probably time out for many tests because it takes a second or two to download the required build. So, we're almost there, just a bit more work and we'll be able to close this. |
|
Ah, there's also a problem with rakudo/rakudo#1501, but this shouldn't affect most of the bots (just bisectable I think). |
|
Not only you can run all bots locally now, but I just pushed a set of commits that make it easy to run tests yourself! It's a bit early to say that this issue is fully resolved as I haven't tested every bot yet (some of them are segfaulting anyway 😢), but at least one bot (unicodable) is passing its tests fully. |
|
|
|
Tackles issue #122 a little bit. This *should* make it work for older zstd versions like 0.5.1 (but I haven't tested it just yet). Also, it should now die with a more helpful message if zstd or lrzip is not installed. I think this adds about 20ms delay every time the code attempts to use some build, and that may seem negligible but it's not. Bisectable normally needs ≈13 steps, which is a ≈0.26s delay. Committable currently uses 28 commits for “releases” or “v6.c” query, and that is a 0.56s delay. Even small things add up in this case, so we can declare this path kinda hot and add some caching… See issue #294.
|
Oops. https://blog.github.com/2018-02-18-deprecation-notice-removing-anonymous-gist-creation/
|
|
Maybe create an user and post from it?
|
Maybe! However, Github does not allow to create more than two accounts, and I'm already over the limit. Also, everyone will be able to post any garbage gists under that account, so potentially it may get banned. So-o-o… I think we should be looking for non-github alternatives, but contributions are welcome. |
|
FWIW I did a lot of improvements lately to this, so it's much better than it was. But still probably not good enough. |
|
See also: #323 |
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.p6that 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:
bloatythat you have to compile yourself…The text was updated successfully, but these errors were encountered: