-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/mutation testing #8
Conversation
needs initial output pushed into this branch before merging
…output-branch_name
- Updated message for unviable mutants, steps to solve it
Based on the type of package it will include the corresponding arguments to be run with. Cases: - if >= 16 mutants on big packages => run big packages using 8 shards - else run big packages without shards - if >= 16 mutants on big packages and >= 120 mutants on small packages => run small packages using 4 shards - else if < 16 mutants on big packages and >= 80 mutants on small packages => run small packages using 4 shards - else run small packages without shards
Test/mutants pr differences
Move Shells from Main Workflow to Composite Action
one question i have here - is this workflow meant to run from any rust- based project, or only the functionally it looks good - just minor changes to align with standards from other workflows in this repo |
I've done the modifications on my repo (https://github.com/ASuciuX/actions/tree/test/move-shell-to-composite) in case there were more commits with fixes if the workflow fails. I've also removed the
It was initially meant to only run on the |
- update readme files - check exit codes - check that files exist before accessing them, otherwise exit - remove shell scripts folder since it was only used in 1 place - update actions versions used
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shipit
feature: mutation testing functional for PR differences in composite actions