-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Load Alloc For Superchain ops integration testing #14021
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #14021 +/- ##
===========================================
- Coverage 46.86% 45.33% -1.54%
===========================================
Files 974 917 -57
Lines 81666 76998 -4668
Branches 759 759
===========================================
- Hits 38275 34906 -3369
+ Misses 40406 39330 -1076
+ Partials 2985 2762 -223
Flags with carried forward coverage won't be shown. Click here to find out more. |
maurelian
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple questions, but overall LGTM
mds1
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM aside from the comment clarifications above
…14021) * fix: test * fix: nit checking to see if adding a new env causes the issue. * fix: unused var * fix: adding branhing logic * fix: copying other pr * fix: clarifications around comments.
…14021) * fix: test * fix: nit checking to see if adding a new env causes the issue. * fix: unused var * fix: adding branhing logic * fix: copying other pr * fix: clarifications around comments.
This is a duplicate of this PR #14007. For an unknown reason I could not get CI to pass on the original PR. I copied the code over and it started work. I tried saving the commit history but kept running into the same issues.
This was an external contribition by @ElliotFriedman and @prateek105.
cc: