Skip to content
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

refactor: Log child process command output on error #679

Merged
merged 1 commit into from
Feb 28, 2022

Conversation

zhemaituk
Copy link
Contributor

A small addition to print out actual error details on child process failure. Refer to #663 for issues details, when build fail for one or another reason, usually connected to configuration error and not library error, but no details are printed out.

@pgrzesik
Copy link
Contributor

Hey @zhemaituk - I believe I've fixed the CI issue, could you please rebase your branch against current master?

A small addition to print out actual error details on child process failure. Refer to serverless#663 for issues details, when build fail for one or another reason, usually connected to configuration error and not library error, but no details are printed out.
@zhemaituk
Copy link
Contributor Author

@pgrzesik done

Copy link
Contributor

@pgrzesik pgrzesik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @zhemaituk 🙇

@pgrzesik pgrzesik changed the title Print out child process command output on error #663 refactor: Log child process command output on error Feb 28, 2022
@pgrzesik pgrzesik merged commit ff11497 into serverless:master Feb 28, 2022
jeanbmar referenced this pull request Mar 3, 2022
…alled correctly.

- Make sure we're consistently quoting arguments.
- Add mergeCommands function to construct a script for docker to run when needed.
- Add getStripMode to run strip correctly for the platform and docker.
@jeanbmar
Copy link

jeanbmar commented Mar 3, 2022

@zhemaituk @pgrzesik this PR should be reverted and and stdio provided to spawn call.
Not every build problem generates a spawn error.

try {
  await spawn(cmd, args, {
    stdio: 'inherit',
});

@pgrzesik
Copy link
Contributor

pgrzesik commented Mar 3, 2022

Could you provide more explanation @jeanbmar? I'm not sure I understand the problem fully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants