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.

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

[scapy] build it more often #12074

Merged
merged 1 commit into from
Jun 17, 2024

Conversation

evverx
Copy link
Contributor

@evverx evverx commented Jun 15, 2024

to let the latest builds be more or less in sync with the upstream repository. It should help CIFuzz to detect known issues better among other things.

Copy link

evverx has previously contributed to projects/scapy. The previous PR was #12050

to let the latest builds be more or less in sync with the upstream
repository. It should help CIFuzz to detect known issues better among
other things.
@jonathanmetzman
Copy link
Contributor

It should help CIFuzz to detect known issues better among other things.

I'm not exactly sure this is the case.

@jonathanmetzman jonathanmetzman merged commit aa07248 into google:master Jun 17, 2024
15 checks passed
@evverx
Copy link
Contributor Author

evverx commented Jun 17, 2024

For example in systemd/systemd#25537 the fuzz target failed on CIFuzz and it was decided to merge it and fix the issues later. Until it reached OSS-Fuzz CIFuzz annoyed contributors because their PRs had nothing to do with CIFuzz failures :-) Ideally OSS-Fuzz should be in sync with repositories. The second option is to reduce the window by building stuff more frequently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants