-
Notifications
You must be signed in to change notification settings - Fork 3
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
.github/workflows: specify core ref in PR desc #307
Conversation
fix test directory for TestAddChainInbound
|
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
In order to keep the `ccip-develop` branch in working condition, we need to make sure the integration test | ||
[written in the CCIP repo](https://github.com/smartcontractkit/ccip/blob/03ae3bbed0e6020be5fa9be26d03af21f152d7dc/core/capabilities/ccip/ccip_integration_tests/ocr3_node_test.go#L37) | ||
In order to keep the `main` branch in working condition, we need to make sure the integration tests | ||
[written in the CCIP repo](https://github.com/smartcontractkit/chainlink/blob/340a6bfdf54745dd1c6d9f322d9c9515c97060bb/deployment/ccip/changeset/initial_deploy_test.go#L19) |
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.
Wait, we run only this single test? It doesn't seem correct, does it? I think as part of this CI action we run every e2e/integration test for ccip 1.6 we have in the chainlink repository. Especially now, when putting more effort to work on these
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.
Yeah we need to rethink these, maybe as a matrix so we can parallelize
core ref: 3b6aacef0c21beca9387b192ce016b5ab6168e46
JIRA: https://smartcontract-it.atlassian.net/browse/CCIP-4181
This PR implements something that has been done in the relayer repos, which is that the author of a PR can specify the commit SHA to use for the Chainlink repo when running the integration tests.
Updated the README.md to reflect the new flow.
Also updated the path of the TestAddChainInbound test, previously that step was not running anything.
After running this flow for a few weeks and seeing it work we can then make the integration tests check required for all PRs to merge.