Vyacheslav Kovalevsky
Vyacheslav Kovalevsky
Found 2 more issues: #3612 #3613
Have been fuzzing VM again, with fixes merged. Haven't found anything in 100M executions (4 days), except for #3701 which is not a bug (i guess). Doesn't mean there are...
> >Haven't found anything in 100M executions > > Do you have any estimation of how much code has been covered? > JMP is hard, but TRY is even harder...
Run it again, with coverage saved Commit: `2b1b9a4fcaaf8181fa8ba532f2897ce5e928df78` [profile.txt](https://github.com/user-attachments/files/18058243/profile.txt) HTML (remove .txt): [cover.html.txt](https://github.com/user-attachments/files/18058246/cover.html.txt)
Don't know how to get profile in `count` mode from `covdata` tool, would be nicer to have
> Don't know how to get profile in `count` mode from `covdata` tool, would be nicer to have I guess I should have compiled harness with `go build -cover -covermode=count`
Showcase (using https://github.com/nspcc-dev/neofs-contract) https://github.com/nspcc-dev/neo-go/assets/40753025/774f2b1b-acee-4afb-9528-9ff3ec321379 It seems like some coverage data is lost when running all package tests at once, need more testing...
Forgot to add reporting if script was already compiled. It does fix problem in the test file on video, but for some reason in other files almost all coverage data...
Fixed the issue. Also the question is, where do we need add the coverage instrumentation? Currently, its only in `TestInvoke()` method, but there are other methods where VM is run.
rebased branch on master