summaryrefslogtreecommitdiffstats
path: root/.github/workflows/cflite_pr.yml (follow)
Commit message (Collapse)AuthorAgeFilesLines
* ci: Switch to Ubuntu 24.04Daan De Meyer2024-06-081-1/+1
|
* CI: revert the mmap_rnd_bits kludgeEvgeny Vereshchagin2024-03-211-1/+0
| | | | | | This reverts commit 2e0c2fb8fb15faeedf213930a4c2a3a6d584101f and commit b7c7498de814b1e9825b43c28e307a7f0af8ffd2 now that https://github.com/actions/runner-images/issues/9491 is closed.
* cifuzz,cflite: set mmap_rnd_bits to 28Evgeny Vereshchagin2024-03-151-0/+1
| | | | | | | to get MSan jobs to work with the latest Ubuntu images. https://github.com/google/sanitizers/issues/1614 https://github.com/actions/runner-images/issues/9491
* ci: Remove custom build step namesJan Janssen2023-09-061-2/+2
| | | | | Putting build matrix details into a build step name is rather useless as the jobs themselves already contain the needed information.
* ci: unpin CFLiteEvgeny Vereshchagin2022-04-261-2/+2
| | | | | | | | The idea was to catch CFLite regressions but since the action itself pulls the latest docker images it can't be pinned properly and issues like https://github.com/google/clusterfuzzlite/issues/91 are going to pop up anyway. Let's unpin it by analogy with CIFuzz and hope it doesn't break very often.
* ci: use CFLite to test forks (including systemd-stable)Evgeny Vereshchagin2022-01-291-0/+39
It's like CIFuzz but unlike CIFuzz it's compatible with forks and it should make it possible to run the fuzzers to make sure that patches backported to them are backported correctly without introducing new bugs and regressions.