You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix all panic errors reported by beacon mock fuzz. Run the following command repeatedly and for long time to check panic: compose new --build-local --validator-types=mock --fuzz && compose auto
Add a fuzz test similar to smoke tests (testutil/compose/smoke/smoke_test.go) in compose which runs beacon mock fuzz on CI.
🧪 Tests
Tested by new automated fuzz tests on CI.
Manually tested on local compose simnet
The text was updated successfully, but these errors were encountered:
Fixes panics found by initial beacon fuzz tests. Also improve efficiency of beacon fuzzer to trigger more panics in charon workflow.
category: test
ticket: #1962
🎯 Problem to be solved
We recently added a flag to compose CLI which runs beacon mock fuzz as part of #1848 . It reports panic caused by random beaconmock responses.
🛠️ Proposed solution
Approved design doc: link
Core team consensus on the proposed solution
Fix all panic errors reported by beacon mock fuzz. Run the following command repeatedly and for long time to check panic:
compose new --build-local --validator-types=mock --fuzz && compose auto
Add a fuzz test similar to smoke tests (testutil/compose/smoke/smoke_test.go) in compose which runs beacon mock fuzz on CI.
🧪 Tests
The text was updated successfully, but these errors were encountered: