-
Notifications
You must be signed in to change notification settings - Fork 84
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
Improve error message if hydra-node crashes #1335
Conversation
563ac81
to
9fddff3
Compare
Transactions CostsSizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using
Script summary
Cost of Init Transaction
Cost of Commit TransactionThis is using ada-only outputs for better comparability.
Cost of CollectCom Transaction
Cost of Close Transaction
Cost of Contest Transaction
Cost of Abort TransactionSome variation because of random mixture of still initial and already committed outputs.
Cost of FanOut TransactionInvolves spending head output and burning head tokens. Uses ada-only UTxO for better comparability.
End-To-End Benchmark ResultsThis page is intended to collect the latest end-to-end benchmarks results produced by Hydra's Continuous Integration system from the latest Please take those results with a grain of salt as they are currently produced from very limited cloud VMs and not controlled hardware. Instead of focusing on the absolute results, the emphasis should be on relative results, eg. how the timings for a scenario evolve as the code changes. Generated at 2024-03-06 07:36:57.041302612 UTC Baseline Scenario
Baseline Scenario
|
9fddff3
to
ac31c3f
Compare
By delaying the connection exception based errors on the websocket client of the test driver, we improve the error output in cases where other assertions provide more info. For example, checkProcessHasNotDied prints the stderr of the crashed hydra-node. Co-authored: Sebastian Nagel <[email protected]>
ac31c3f
to
05e8859
Compare
By delaying the connection exception based errors on the websocket client of the test driver, we improve the error output in cases where other assertions provide more info. For example, checkProcessHasNotDied prints the stderr of the crashed hydra-node.
This is something @cardenaso11 and me did when pairing today.
Instead of the often seen
ConnectionClosed
non-saying error we now (more consistently) get the reason why the hydra-node crashed: