Closed marcelo-gonzalez closed 1 week ago
it seems that skip_epoch.py still fails after this... but it's for an unrelated reason
Attention: Patch coverage is 0%
with 1 line
in your changes missing coverage. Please review.
Project coverage is 71.66%. Comparing base (
642f6a0
) to head (302bb83
).
Files | Patch % | Lines |
---|---|---|
chain/client/src/client_actor.rs | 0.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
cc @wacban
@marcelo-gonzalez To what do I owe the cc? :)
@marcelo-gonzalez To what do I owe the cc? :)
ah, well just wanted to cc you so youre aware since it looks like your area. not much else to do with this particular PR of course :) . But I prob could have added this in the cc message... it looks like even after applying this PR, skip_epoch.py still fails right after c16ca0b7c8f1b92c0597cc7519aa5c54eb9c8a90, which looks like the commit that added this function. will provide some more details later
Ah I see, is it my PR that broke this test?
Ah I see, is it my PR that broke this test?
yea I think it looks that way.. did a git bisect and it landed on that one
Subtracting 1 from the smallest chunk height included crashes when it's zero, which can actually happen in many tests, and is currently causing the skip_epoch.py test to fail