-
Notifications
You must be signed in to change notification settings - Fork 1.9k
CRE Fix Chain Reads Tests in Response to Read Limits Enforcement #20762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
| defer func() { | ||
| if r := recover(); r != nil { | ||
| runtime.Logger().Error("recovered from panic", "recovered", r, "stack", string(debug.Stack())) | ||
| err = fmt.Errorf("panic: %v", r) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Return error instead of panic to clean up logs
| } | ||
| } | ||
| t.Logger.Error(fmt.Sprintf(format, args...)) | ||
| panic(fmt.Sprintf(format, args...)) // panic to stop execution |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
panic here was redundat as require always calls FailNow, which panics to abort workflow execution
* core/services/workflows/v2: expand limited ChainSet method set * CRE Fix Chain Reads Tests in Response to Read Limits Enforcement (#20762) * Improve logging * addd testcase name to cfg * Refactor EVM Read Test * remove redundant method * fix linter * go generate * bump common * Switch to ChipTestSink * Remove concurrent execution to avoid nonce race during workflow removal * Fix nolint --------- Co-authored-by: Dmytro Haidashenko <34754799+dhaidashenko@users.noreply.github.com> Co-authored-by: Dmytro Haidashenko <dmytro.haidashenko@smartcontract.com>



Chain Read limits enforcement broke the CRE EVM Read Tests. To fix them, the test was split into smaller parts, each tested separately.