CyclopsMC / IntegratedDynamics / 22277497989

46%

push

github

Add nightly fuzzing CI for random network crash detection (#1607)

* Initial plan

* Add fuzzing game test and nightly fuzzing workflow

Co-authored-by: rubensworks <440384+rubensworks@users.noreply.github.com>

* Run workflow every hour

* Use actual placement logic in fuzzing tests

* Use registries to determine fuzzing elements

* Use proper generics in NetworkFuzzer

* Improve reader context fuzzing randomness

* Throw exceptions instead of logging during fuzzing errors

* Report issue on fuzzing failures

* Mention fuzzing logs within created issue

* Fix fuzzing using incorrect variable IDs

* Place fuzzing context blocks for writers

* Place multiple variable stores during fuzzing if needed

* Lower chance of TARGETENTITY operator during fuzzing

* Fix parts overwriting other parts during fuzzing

* Fix value type category handling during fuzzing

* Place at least one part during fuzzing

* Don't throw fuzzing exception when no more space for writers

* Also fuzz random constant values

* Fallback to fuzzing random values if operator chain is empty

* Improve variability of fluid and machine reader fuzzing contexts

* Save fuzzing structure even on exceptions

* Add deterministic seed to fuzzer

* Run 1000 fuzzing iterations every night in CI

* Also save entities within fuzzing structure files

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: rubensworks <440384+rubensworks@users.noreply.github.com>
Co-authored-by: Ruben Taelman <rubensworks@gmail.com>

2665 of 8848 branches covered (30.12%)

Branch coverage included in aggregate %.

12043 of 24171 relevant lines covered (49.82%)

2.36 hits per line