Add support for building private dependencies in CI #35733

Triggered via pull request November 18, 2024 23:27

sjonpaulbrown

synchronize #6727

jp/update-ci

Status Failure

Total duration 11m 2s

Artifacts –

ci.yml

on: pull_request

Docker Build

8m 52s

Create Dynamic Integration Test Package Matrix

24s

Create Dynamic Test Matrix

18s

Create Dynamic Unit Test Insecure Package Matrix

22s

Tidy

30s

Matrix: Lint

Matrix: Integration Tests

Matrix: integration-test-others

Matrix: unit-test

Matrix: unit-test-insecure

Annotations

15 errors and 106 warnings

Integration Tests (Collection Integration Tests, make -C integration collection-tests, ubuntu-lat...

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (Verification Integration Tests, make -C integration verification-tests, ubuntu...

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (Access Cohort3 Integration Tests, make -C integration access-cohort3-tests, ub...

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (Access Cohort2 Integration Tests, make -C integration access-cohort2-tests, ub...

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (Upgrade Integration Tests, make -C integration upgrades-tests, ubuntu-latest)

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (Consensus Integration Tests, make -C integration consensus-tests, ubuntu-latest)

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (BFT (Gossipsub) Integration Tests, make -C integration bft-gossipsub-tests, ub...

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (Execution Integration Tests, make -C integration execution-tests, ubuntu-latest)

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (Network Integration Tests, make -C integration network-tests, ubuntu-latest)

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (MVP Integration Tests, make -C integration mvp-tests, ubuntu-latest)

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (Ghost Integration Tests, make -C integration ghost-tests, ubuntu-latest)

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (Epoch Cohort1 Integration Tests, make -C integration epochs-cohort1-tests, bui...

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (BFT (Protocol) Integration Tests, make -C integration bft-protocol-tests, buil...

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (Epoch Cohort2 Integration Tests, make -C integration epochs-cohort2-tests, bui...

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Integration Tests (Access Cohort1 Integration Tests, make -C integration access-cohort1-tests, bu...

The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.

Create Dynamic Test Matrix

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Create Dynamic Test Matrix

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Create Dynamic Unit Test Insecure Package Matrix

Create Dynamic Integration Test Package Matrix

Tidy

Lint (./insecure/)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4, golangci/golangci-lint-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Lint (./integration/)

Unit Tests (network/p2p/node)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4, nick-fields/retry@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Unit Tests (engine/execution/ingestion)

Unit Tests Insecure (insecure/integration/functional/test/gossipsub/rpc_inspector)

Unit Tests (network/test/cohort1)

Unit Tests (module/dkg)

Unit Tests (network)

Unit Tests (engine/execution/computation)

Unit Tests (network/test/cohort2)

Unit Tests (utils)

Unit Tests (storage)

Unit Tests (state)

Unit Tests (admin)

Unit Tests (network/p2p)

Unit Tests (engine/collection)

Unit Tests (network/alsp)

Unit Tests (engine/common)

Integration Tests Others (integration)

Unit Tests (consensus)

Unit Tests (others)

Lint (./)

Unit Tests (module)

Unit Tests (network/p2p/connection)

Unit Tests Insecure (insecure/integration/functional/test/gossipsub/scoring)

Unit Tests (fvm)

Unit Tests (network/p2p/scoring)

Unit Tests (engine/verification)

Unit Tests (ledger)

Unit Tests Insecure (insecure)

Unit Tests (cmd)

Unit Tests (engine/execution)

Attempt 1 failed. Reason: Child_process exited with error code 2

Unit Tests (engine/execution)

Attempt 2 failed. Reason: Child_process exited with error code 2

Unit Tests (engine/consensus)

Unit Tests (engine)

Unit Tests (engine/access)

Attempt 1 failed. Reason: Child_process exited with error code 2

Docker Build

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@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/

Integration Tests (Collection Integration Tests, make -C integration collection-tests, ubuntu-lat...