Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[CICD] Improve test / fuzz execution criteria #402

Open
sea212 opened this issue Dec 8, 2021 · 0 comments
Open

[CICD] Improve test / fuzz execution criteria #402

sea212 opened this issue Dec 8, 2021 · 0 comments
Labels
p:low Low priority, resolution of this issue can wait t:enhancement The issue described an enhancement

Comments

@sea212
Copy link
Member

sea212 commented Dec 8, 2021

All unit and fuzz tests are executed in any case, even if none of the actual source code was changed. A massive amount of required time for workflows can be reduced by selectively executing unit and fuzz tests.

Figure out a way to determine whether changes in relevant code happened and execute the job only in that case. As a bonus, selectively execute unit and fuzz tests only on files / crates that actually contain changes.
@sea212 sea212 added p:low Low priority, resolution of this issue can wait t:enhancement The issue described an enhancement labels Dec 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
p:low Low priority, resolution of this issue can wait t:enhancement The issue described an enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sea212