-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need more build detail #53
Comments
Hey @qiwang97, GitHub Actions by default does print the logs of whatever commands are used in an action. The only thing that could be done to maybe improve logging is add console.logs to the outputs of the execSync functions in the action. Essentially wherever you see:- execSync('something'); you would replace that with console.log(execSync('something')) Though I don't know how much that would help and it might even make up your logs. Regardless I would encourage you to fork the repo and make that change, or I can also make a branch with this variant that you can try if you want. On a side node. It is also a little strange that the build runs slower when the output from docker isn't printed out, I would assume it should run faster in that case. |
Thanks and i will try. I just want to see which step is slow and find the reason. |
Closing this action due to inactivity. Please reopen it if this issue is still relevant to you |
I set
usedocker: true
in my action. But it runs slow when build with docker without stdout.Is there anyway to show more build details when use with docker?
The text was updated successfully, but these errors were encountered: