Skip to content

Comments

fix: use expected_exception instead of error field for unexpected_success status#3244

Merged
rakita merged 1 commit intobluealloy:mainfrom
leopardracer:patch-2
Dec 22, 2025
Merged

fix: use expected_exception instead of error field for unexpected_success status#3244
rakita merged 1 commit intobluealloy:mainfrom
leopardracer:patch-2

Conversation

@leopardracer
Copy link
Contributor

Fix incorrect JSON output in blockchain test runner. When a transaction unexpectedly succeeds (status: "unexpected_success"), the output previously included an "error" field with the expected exception message, which was misleading since no actual error occurred. Changed the JSON output to use "expected_exception" field instead of "error" to accurately reflect the execution state.

@codspeed-hq
Copy link

codspeed-hq bot commented Dec 20, 2025

CodSpeed Performance Report

Merging #3244 will not alter performance

Comparing leopardracer:patch-2 (8ed60b3) with main (7b505e6)

Summary

✅ 173 untouched

@rakita rakita merged commit ba5bb55 into bluealloy:main Dec 22, 2025
31 checks passed
@github-actions github-actions bot mentioned this pull request Dec 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants