Tutorial with distributed github workload?

[tomato42]

I have created a workload that uses multiple github actions workers to run mutation testing in Github CI, the PR implementing it is here: tlsfuzzer/python-ecdsa#156

I wonder if you'd be interested in me contributing a chapter to cosmic-ray documentation that describes that.

Problem is, that I've done that in a slightly work-around-y way: I've split up an combined the SQLite database using sqlite itself, not using python code.

Besides that, I have to say that with few speed-ups to the test suite, to make it execute in just few seconds, running mutation testing on 20 workers for 10 minutes executes almost a third of all the mutations, so the 99.9% confidence interval for survival rate is around 1 percentage point.

[abingham]

Sure, a how-to for that would be great. The docs would benefit from things like that. Thanks! Sent from ProtonMail mobile

…

-------- Original Message --------

On Dec 31, 2023, 05:50, Hubert Kario wrote: I have created a workload that uses multiple github actions workers to run mutation testing in Github CI, the PR implementing it is here: [tlsfuzzer/python-ecdsa#156](tlsfuzzer/python-ecdsa#156) I wonder if you'd be interested in me contributing a chapter to cosmic-ray documentation that describes that. Problem is, that I've done that in a slightly work-around-y way: I've split up the SQLite database using sqlite itself, not using python code. Besides that, I have to say that with few speed-ups to the test suite, to make it execute in just few seconds, running mutation testing on 20 workers for 10 minutes executes almost a third of all the mutations, so the 99.9% confidence interval for survival rate is around 1 percentage point. — Reply to this email directly, [view it on GitHub](#542), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAATK6DZOAEFBKLGFBMDCF3YMFGSFAVCNFSM6AAAAABBIGLMRGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DCMBTGQ3DSMY). You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>