You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge #6512: ci: avoid killing the CI script itself on functional test error
8413621 ci: avoid killing the CI script itself on functional test error (UdjinM6)
Pull request description:
## Issue being fixed or feature implemented
We kill CI script on test errors and it can't collect logs.
## What was done?
Set `CI_FAILFAST_TEST_LEAVE_DANGLING` env variable to avoid that.
## How Has This Been Tested?
1a69226: https://gitlab.com/dashpay/dash/-/jobs/8727924503
## Breaking Changes
## Checklist:
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added or updated relevant unit/integration/functional/e2e tests
- [ ] I have made corresponding changes to the documentation
- [ ] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
ACKs for top commit:
PastaPastaPasta:
utACK 8413621
Tree-SHA512: 9fcebcc22da2461f549bdf8b6c476df5a6537b4fdd1d147c473aa5ed8eef40604f5ed9df1414fefb0c920c18c4b3bffa8c82ee129fa90e9f785fff4f5cca9681
Copy file name to clipboardExpand all lines: .gitlab-ci.yml
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,7 @@ image: "ubuntu:jammy"
3
3
variables:
4
4
DOCKER_DRIVER: overlay2
5
5
FAST_MODE: "false"# when "true", only run linter on arm and unit/functional tests on linux64, skip everything else
6
+
CI_FAILFAST_TEST_LEAVE_DANGLING: "1"# Gitlab CI does not care about dangling process and setting this variable avoids killing the CI script itself on error
0 commit comments