-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Dockerize Integration Tests #670
Conversation
|
09ebcf1
to
f228618
Compare
8a31706
to
7fc5bea
Compare
46918cd
to
a1521e4
Compare
4cd623c
to
e3705b4
Compare
4c50b40
to
d56a290
Compare
e13ebc9
to
87350f4
Compare
integration-tests/hardhat.config.ts
Outdated
ovm: true, | ||
}, | ||
}, | ||
solidity: '0.7.6', | ||
ovm: { | ||
solcVersion: '0.7.6', | ||
solcVersion: '0.7.6-allow_kall_2', // temporary until we fix the build for 0.7.6 |
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.
Should this be an env var with this as the default value?
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.
No this is not supposed to be configurable. Kall support is exposed by the compiler now so this change is no longer required.
ops/docker/Dockerfile.monorepo
Outdated
# copy over solc to save time building (35+ seconds vs not doing this step) | ||
COPY --from=downloader solc /root/.cache/hardhat-nodejs/compilers/linux-amd64/solc-linux-amd64-v0.7.6+commit.7338295f | ||
COPY --from=downloader ovm-solc /root/.cache/hardhat-nodejs/compilers/ovm/0.7.6.js | ||
COPY --from=downloader ovm-solc /root/.cache/hardhat-nodejs/compilers/ovm/0.7.6-allow_kall_2.js |
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.
Can we copy the compilers
directory over so that we don't need to hard code versions here?
This will be nice because it will allow us to run the integration tests in
Is this solved for or should we open another issue for this specifically? I'd like to be able to run the integration tests against a testnet deployment, so things like the timeout need to be very configurable. |
One additional thing is that if we want to be able to run the integration tests against something that is not a testnet, we will need a hardhat environment to act as L1. We do not publish the hardhat image from this repo, I have published a hardhat repo in the past at |
87350f4
to
416a67d
Compare
ops/scripts/integration-tests.sh
Outdated
|
||
if [[ ! -z "$URL" ]]; then | ||
# get the addrs from the URL provided | ||
ADDRESSES=$(curl --silent --retry-connrefused --retry $RETRIES --retry-delay 5 $URL) |
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.
--fail
|
||
# wait for the sequencer to be up | ||
curl \ | ||
--silent \ |
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.
--fail --show-error
* test: add docker image for integration tests * feat: add to docker-compose with scale 0 * ci: run and publish integration tests to dockerhub * test: add option to not bring network up for docker integration tests * chore: add --fail --show-error to curl
Fixes #654. depends on #669