-
Notifications
You must be signed in to change notification settings - Fork 20
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: CI failed to run the op e2e tests #85
Conversation
yes, I tested it locally, all tests are passed.
it is werid |
hmm that's not the right way to test PR like this. to test CI, you need to check if the CI does what it's supposed to do -- by examining the logs :) |
Discussed offline. FILTER is probably the root cause. let's
|
test-e2e-op: clean-e2e install-babylond | ||
@go test -mod=readonly -timeout=25m -v $(PACKAGES_E2E_OP) -count=1 --tags=e2e_op | ||
|
||
FILTER ?= . | ||
test-e2e-op-filter: clean-e2e install-babylond | ||
@go test -mod=readonly -timeout=25m -v $(PACKAGES_E2E_OP) -count=1 --tags=e2e_op --run ^$(FILTER)$ |
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.
Good idea on having FILTER
for testing certain case 👍
Summary
This PR:
e2e_op
job to set up the devnet data for OP e2e tests, addressing the issue where the devnet data does not exist. fix: op e2e test #76 (comment)e2e_op
job issue: "no test to run"Test Plan
To trigger the CI to check if the op e2e tests work fine.