Skip to content
test

feat(script): support custom create2 deployer #16655

Sign in to view logs

feat(script): support custom create2 deployer

feat(script): support custom create2 deployer #16655

Triggered via pull request November 9, 2024 17:00
@jsvisajsvisa
synchronize #9278
jsvisa:script-deployer
Status Failure
Total duration 9m 14s
Artifacts –

test.yml

on: pull_request
docs
1m 16s
docs
doctest
2m 46s
doctest
codespell
11s
codespell
clippy
1m 13s
clippy
rustfmt
13s
rustfmt
forge-fmt
1m 21s
forge-fmt
crate-checks
2m 50s
crate-checks
nextest  /  build matrices
4s
nextest / build matrices
Matrix: nextest / test
ci-success
4s
ci-success
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 13 warnings
clippy
Process completed with exit code 101.
nextest / test integration (2/3) (x86_64-unknown-linux-gnu)
Process completed with exit code 101.
nextest / test integration (3/3) (x86_64-unknown-linux-gnu)
Process completed with exit code 101.
nextest / test integration / issue-repros (1/2) (x86_64-unknown-linux-gnu)
Process completed with exit code 101.
nextest / test integration / issue-repros (2/2) (x86_64-unknown-linux-gnu)
Process completed with exit code 101.
nextest / test integration / external (1/2) (x86_64-unknown-linux-gnu)
Process completed with exit code 101.
nextest / test integration / external (2/2) (x86_64-unknown-linux-gnu)
Process completed with exit code 101.
nextest / test unit (x86_64-unknown-linux-gnu)
Process completed with exit code 101.
nextest / test integration (1/3) (x86_64-unknown-linux-gnu)
Process completed with exit code 101.
nextest / test unit (x86_64-pc-windows-msvc)
Process completed with exit code 1.
nextest / test integration (2/3) (x86_64-pc-windows-msvc)
Process completed with exit code 1.
nextest / test integration (1/3) (x86_64-pc-windows-msvc)
Process completed with exit code 1.
nextest / test integration (3/3) (x86_64-pc-windows-msvc)
Process completed with exit code 1.
ci-success
Process completed with exit code 1.
nextest / build matrices
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nextest / test integration (2/3) (x86_64-unknown-linux-gnu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nextest / test integration (3/3) (x86_64-unknown-linux-gnu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nextest / test integration / issue-repros (1/2) (x86_64-unknown-linux-gnu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nextest / test integration / issue-repros (2/2) (x86_64-unknown-linux-gnu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nextest / test integration / external (1/2) (x86_64-unknown-linux-gnu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nextest / test integration / external (2/2) (x86_64-unknown-linux-gnu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nextest / test unit (x86_64-unknown-linux-gnu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nextest / test integration (1/3) (x86_64-unknown-linux-gnu)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nextest / test unit (x86_64-pc-windows-msvc)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nextest / test integration (2/3) (x86_64-pc-windows-msvc)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nextest / test integration (1/3) (x86_64-pc-windows-msvc)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nextest / test integration (3/3) (x86_64-pc-windows-msvc)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/