Showing results for 
Search instead for 
Did you mean: 
Copilot Lvl 3
Message 1 of 9
8 Replies
GitHub Partner
Message 2 of 9

Re: Fail golang tests

Hi Smolevich,

Could you share the complete debug logs of the jobs and steps in your workflow, so that we can analyze the root cause?
To get the debug logs, you need to add two Secrets (ACTIONS_RUNNER_DEBUG and ACTIONS_STEP_DEBUG), and set their value to be true.


Copilot Lvl 3
Message 3 of 9

Re: Fail golang tests

Yes, i try it 

Copilot Lvl 3
Message 4 of 9
GitHub Partner
Message 5 of 9

Re: Fail golang tests

@Smolevich Thanks for your reply. It seems that the logs you shared does not include the debug logs. After you add the two Secrets (ACTIONS_RUNNER_DEBUG and ACTIONS_STEP_DEBUG), you need to re-run the workflow and get the debug logs from the new run.

Copilot Lvl 3
Message 6 of 9

Re: Fail golang tests

After add new secrets i pushed new commit and link on new full archive log

Copilot Lvl 3
Message 7 of 9

Re: Fail golang tests

but i don't find lines such as

##[debug]Evaluating condition for step: 'Run golang tests'
##[debug]Parsing expression: <success()>

in logs

Copilot Lvl 3
Message 8 of 9

Re: Fail golang tests

@BrightRan , i delete secrets and add againg , pushed new commits and debug info was founded in logs

Copilot Lvl 2
Message 9 of 9

Re: Fail golang tests

Hey @Smolevich 


I see the following error in your logs:


flag provided but not defined: -coverprofilevers




In your YAML for the headers step you have 


 Based on the travis file and the other tests, I believe it should just be 



Reference from travis file: