How do I find the cause of a failure? #943
Replies: 2 comments 4 replies
-
A great way to get help, is to paste a stripped down version of your Tell us what version of |
Beta Was this translation helpful? Give feedback.
2 replies
-
I think a bug around promise error handling was introduced in 4.42.0. See #946 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to use gitlab-ci-local to test my
.gitlab-ci.yml
file, but it fails without giving any further details. How can I find out what exactly is going wrong? I did look at the --help info, but it did not appear to give any way to enable debug logging or something like that.This is on Windows 10. I installed gitlab-ci-local by running
npm install -g gitlab-ci-local
, which gave no errors. I know it can find and parse the.gitlab-ci.yml
file, because the --list and --preview commands work. Here is the complete output it gives when I try to build the project using the commandgitlab-ci-local assembleRelease
:It just says FAIL without providing any detail about what failed or why. There is a
.\.gitlab-ci-local\builds
directory that appears to contain a correct copy of the source code, and a.\.gitlab-ci-local\output\assembleRelease.log
file which is empty.How can I find out more about what exactly went wrong and what the cause was?
Beta Was this translation helpful? Give feedback.
All reactions