Open nicola-lunghi opened 3 months ago
confirmed without debug the error is printed twice and the step succeed
We implemented retries:
The messages that are logged out are info logs, they occur multiple times due to the multiple retries. The messages include a the "attempt" not. In the end it worked out, hence the successful step.
But I agree we can make this less confusing by making clear that this error occurred but that we are retrying and also log out when it succeeded.
hi the issue here is that even if the step fails in getting a token the jobs continues as the step is marked as successful (the job fail later because there's no token)
if i enable the debug run instead the step is correctly marked as failed (rerun action -> enable debug logging)
it's not an issue with the error message
if you look at this picture the step is marked as passed
the job fail later because there's no token
Okay in that case something is definitely broken 🤔 Can you reliably reproduce it? Or do you see the problem intermittently?
I have the following step in my workflow
The action fails but the step result is not failure
Error from the step repositories not set, creating token for all repositories for given owner "" Failed to create token for "" (attempt 1): 'Expiration time' claim ('exp') is too far in the future - https://docs.github.com/enterprise-server@3.8/rest
The issue seems to be random as relaunching the job with debug enabled now it show the step as failed