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
For #2509 needs, I had to comment out one driver test that started failing all of a sudden between this and this action.
Few facts:
The failure is not caused by code change, because there were several PRs that contained all the recent commits and passed successfully CI before 8th of March evening.
I compared the tools used (in successful vs failed action run) and all dependencies are same:
# Description
#2526 started limiting the amount of gas the driver allows per solution.
However, the limit was only applied after solutions had been ranked and
participated in the autopilot's auction. This lead to large settlements
effectively clogging the auction cycle as solvers would continue to win
the competition but then fail to submit.
This PR filters out such solutions already in the driver internal
ranking phase so that too large settlements never participate as
solution candidate.
# Changes
- [x] Make `Gas::new` return an error if gas limit is too high
- [x] Introduce a new solver error type that solver engines are notified
about.
## How to test
Adjusted high gas limit driver test
## Related Issues
Fixes#2511 (or rather makes it obsolete)
Background
For #2509 needs, I had to comment out one driver test that started failing all of a sudden between this and this action.
Few facts:
Download action repository 'actions/checkout@v3' (SHA:f43a0e5ff2bd294095638e18286ca9a3d1956744)
Download action repository 'foundry-rs/foundry-toolchain@v1' (SHA:362aa1be8f31305295acb1032271acd5e9b99312)
Download action repository 'Swatinem/rust-cache@v2' (SHA:23bce251a8cd2ffc3c1075eaa2367cf899916d84)
Download action repository 'taiki-e/install-action@nextest' (SHA:86942e25b57085bbdddea3ed90d56728b106b0aa)
Acceptance criteria
The driver test high_gas_limit is uncommented and passes CI.
The text was updated successfully, but these errors were encountered: