-
Notifications
You must be signed in to change notification settings - Fork 295
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
[ci] Reenable uniswap e2e tests #1367
Labels
A-devops
Area: Devops. E.g. CI / build systems
Comments
ludamad
added a commit
that referenced
this issue
Aug 2, 2023
ludamad
added a commit
that referenced
this issue
Aug 2, 2023
ludamad
added a commit
that referenced
this issue
Aug 2, 2023
Maybe possible to do like https://github.com/PaulRBerg/foundry-template/blob/main/.github/workflows/ci.yml. |
Interesting what's this FOUNDRY_FUZZ_SEED voodoo? |
ludamad
changed the title
[ci] Stabilize uniswap e2e tests
[ci] Reenable uniswap e2e tests
Aug 2, 2023
4 tasks
LHerskind
added a commit
that referenced
this issue
Aug 4, 2023
Fixes #1367 Use a chain dump instead of forking for uniswap tests. The sandbox is still using the fork. # Checklist: Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge. - [ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag. - [ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code. - [ ] Every change is related to the PR description. - [ ] I have [linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) this pull request to relevant issues (if any exist).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seem to be rate limited or something. Would be good to minimize reliance on infura (minimizing our API rate limits is probably important as CI might become really active at points)
EDIT: May be temporary outage, see below, likely just waiting
The text was updated successfully, but these errors were encountered: