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
We have several Hive engine tests failing, see e.g. here as some latest run.
Picking out the following failing tests:
These should be (I guess?) a somewhat easy fix, seems there is mainly the error code for some scenario wrong:
"FAIL (ForkchoiceUpdatedV3 To Request Shanghai Payload, Null Beacon Root): Expected error code on EngineForkchoiceUpdatedV3: want=-38003, got=-32602"
This might also be easiest to fix optimistically, so not to directly validate by setting up Hive (at least if one has not the setup locally and easily available) but just look at the scenario, give this a fix and see on next Hive run if things pass.
Note that there are more failing tests. Just picking out these ones to have one place for one type of failure to work on and eventually discuss and exchange.
The text was updated successfully, but these errors were encountered:
Hmm, honestly: why not? Most of our bug fixing is done fully independent from Hive. And when Hive points to some misbehavior and we can confirm for ourselves this is misbehavior we can very well fix that without all the Hive setup?
We have several Hive engine tests failing, see e.g. here as some latest run.
Picking out the following failing tests:
These should be (I guess?) a somewhat easy fix, seems there is mainly the error code for some scenario wrong:
"FAIL (ForkchoiceUpdatedV3 To Request Shanghai Payload, Null Beacon Root): Expected error code on EngineForkchoiceUpdatedV3: want=-38003, got=-32602"
This might also be easiest to fix optimistically, so not to directly validate by setting up Hive (at least if one has not the setup locally and easily available) but just look at the scenario, give this a fix and see on next Hive run if things pass.
Note that there are more failing tests. Just picking out these ones to have one place for one type of failure to work on and eventually discuss and exchange.
The text was updated successfully, but these errors were encountered: