Skip to content

Identity staking improvement #8115

Identity staking improvement

Identity staking improvement #8115

Triggered via pull request September 20, 2024 08:13
Status Cancelled
Total duration 27m 7s
Artifacts 5

ci.yml

on: pull_request
set-condition
8s
set-condition
parachain-dynamic-contract-test
19s
parachain-dynamic-contract-test
parachain-build-dev
25m 31s
parachain-build-dev
bitacross-build
1m 11s
bitacross-build
parachain-clippy
13m 38s
parachain-clippy
parachain-unit-test
6m 24s
parachain-unit-test
parachain-runtime-test
25m 31s
parachain-runtime-test
Matrix: tee-check
Matrix: parachain-ts-test
Matrix: identity-single-worker-test
Matrix: identity-multi-worker-test
Matrix: bitacross-worker-test
push-docker
0s
push-docker
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 12 warnings
parachain-runtime-test
Canceling since a higher priority waiting request for 'General CI-refs/pull/3074/merge' exists
parachain-runtime-test
The operation was canceled.
parachain-build-dev
Canceling since a higher priority waiting request for 'General CI-refs/pull/3074/merge' exists
parachain-build-dev
The operation was canceled.
Variables should be defined before their use: tee-worker/build.Dockerfile#L135
UndefinedVar: Usage of undefined variable '$LD_LIBRARY_PATH' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: tee-worker/build.Dockerfile#L133
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: tee-worker/build.Dockerfile#L134
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Sensitive data should not be used in the ARG or ENV commands: tee-worker/build.Dockerfile#L62
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SGX_COMMERCIAL_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: tee-worker/build.Dockerfile#L25
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: tee-worker/build.Dockerfile#L26
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: tee-worker/build.Dockerfile#L27
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: tee-worker/build.Dockerfile#L28
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: tee-worker/build.Dockerfile#L29
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Sensitive data should not be used in the ARG or ENV commands: tee-worker/build.Dockerfile#L61
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SGX_COMMERCIAL_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: tee-worker/build.Dockerfile#L100
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: tee-worker/build.Dockerfile#L101
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Artifacts

Produced during runtime
Name Size
litentry-bitacross
188 MB
litentry-identity
194 MB
litentry~litentry-parachain~QD698V.dockerbuild
27.9 KB
litentry~litentry-parachain~TYYVJM.dockerbuild
194 KB
litentry~litentry-parachain~WL0U5Y.dockerbuild
50.5 KB