René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Set up CIFuzz to run fuzz targets continuously","articleBody":"# Feature or enhancement\r\n\r\nOSS-Fuzz offers [CIFuzz](https://google.github.io/oss-fuzz/getting-started/continuous-integration/), a collection of GitHub actions that can be used for running fuzz targets based on [the existing OSS-Fuzz configuration](https://github.com/google/oss-fuzz/tree/master/projects/cpython3) similarly to running unit tests in CI.\r\n\r\n\r\n\r\n# Pitch\r\n\r\nCPython has been tested by OSS-Fuzz for a few years. The tool has helped discover multiple issues like #91466, #102509, and #106057. However, there is a tendency to leave [builds](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=60831) or [individual tests](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=51574) broken for a while. The issues are usually caused by changes in CPython code, and current testing performed in GitHub actions and Buildbot misses some cases like compiling CPython with memory sanitizer.\r\n\r\nCIFuzz can help identify issues when they are created, and passing tests can be made a requirement for a successful status of a pull request. This can help prevent new issues of this kind from being merged in the main branch.\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-107653\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/illia-v","@type":"Person","name":"illia-v"},"datePublished":"2023-08-05T10:55:00.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/107652/cpython/issues/107652"}