-
Notifications
You must be signed in to change notification settings - Fork 412
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
fix: failing ci tests for SmartProvider
and OpStackIsm.t.sol
#3148
Conversation
|
and OpStackIsm.t.sol
SmartProvider
and OpStackIsm.t.sol`
SmartProvider
and OpStackIsm.t.sol`SmartProvider
and OpStackIsm.t.sol
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #3148 +/- ##
==========================================
- Coverage 67.51% 0.00% -67.52%
==========================================
Files 101 1 -100
Lines 1022 16 -1006
Branches 106 0 -106
==========================================
- Hits 690 0 -690
+ Misses 292 16 -276
+ Partials 40 0 -40
|
### Description Remove hard-coding of min block number and topic1 value. ### Drive-by changes Add convenience `isAddress` util function ### Related issues #3148 ### Backward compatibility Yes
…erlane-xyz#3148) ### Description - Problem: OpStackIsm.t.sol was failing because of very stale block number for fork Fix: Excluding foundry fork testing from CI and updating block number - Problem: SmartProvider getLogs tests failing because the the results end up being an empty list and getConfirmations results a smaller number of confirmations than expected (712 vs 1705184) fix: excluded from ci ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Manual
### Description Remove hard-coding of min block number and topic1 value. ### Drive-by changes Add convenience `isAddress` util function ### Related issues hyperlane-xyz#3148 ### Backward compatibility Yes
Description
Problem: OpStackIsm.t.sol was failing because of very stale block number for fork
Fix: Excluding foundry fork testing from CI and updating block number
Problem: SmartProvider getLogs tests failing because the the results end up being an empty list and getConfirmations results a smaller number of confirmations than expected (712 vs 1705184)
fix: excluded from ci
Drive-by changes
None
Related issues
None
Backward compatibility
Yes
Testing
Manual