Skip to content
ci

chore(e2e): e2e test for activating and unbonded in mempool #157

Sign in to view logs

chore(e2e): e2e test for activating and unbonded in mempool

chore(e2e): e2e test for activating and unbonded in mempool #157

Triggered via pull request October 4, 2024 17:03
@Lazar955Lazar955
synchronize #71
lazar/active-unbond-e2e
Status Success
Total duration 5m 22s
Artifacts 1

ci.yml

on: pull_request
docker_pipeline  /  docker_build
3m 11s
docker_pipeline / docker_build
lint_test  /  build
1m 14s
lint_test / build
lint_test  /  lint
1m 9s
lint_test / lint
lint_test  /  unit-tests
5m 0s
lint_test / unit-tests
lint_test  /  integration-tests
5m 12s
lint_test / integration-tests
lint_test  /  check-mock-gen
0s
lint_test / check-mock-gen
docker_pipeline  /  dockerhub_publish
0s
docker_pipeline / dockerhub_publish
docker_pipeline  /  ecr_publish
0s
docker_pipeline / ecr_publish
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Variables should be defined before their use: Dockerfile#L49
UndefinedVar: Usage of undefined variable '$VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Artifacts

Produced during runtime
Name Size
babylonlabs-io~vigilante~RV4IFU.dockerbuild
40.8 KB