-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
fix(publishing-bumped-packages): look for status code instaead of stderr #36004
Conversation
This pull request was exported from Phabricator. Differential Revision: D42836212 |
cwd: packageAbsolutePath, | ||
shell: true, | ||
stdio: 'pipe', | ||
encoding: 'utf-8', | ||
}); | ||
if (stderr) { | ||
if (status !== 0) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we maybe get back both stderr and status and if status is != 0 print both status and stderr? To get better understanding of what's failing 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we maybe get back both stderr and status and if status is != 0 print both status and stderr? To get better understanding of what's failing 👍
Yeah, somehow missed that, will get it back
…err (facebook#36004) Summary: Pull Request resolved: facebook#36004 Changelog: [Internal] This fixes CircleCI job, which is responsible for publishing bumped packages. We should not check for `stderr`, apparently `npm` uses it to store debug information: - npm/npm#118 (comment) So we've tried to use this on 0.71-stable before and it succesfully published one package, but have exited right after it because `stderr` was not empty Reviewed By: cipolleschi Differential Revision: D42836212 fbshipit-source-id: a09cb7adc750cbb9e735bdefbe92050f9f5767c6
This pull request was exported from Phabricator. Differential Revision: D42836212 |
e5597b5
to
8399050
Compare
Base commit: e91e468 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM modulo what @kelset also suggested
This pull request has been merged in 9856c33. |
…err (#36004) Summary: Pull Request resolved: #36004 Changelog: [Internal] This fixes CircleCI job, which is responsible for publishing bumped packages. We should not check for `stderr`, apparently `npm` uses it to store debug information: - npm/npm#118 (comment) So we've tried to use this on 0.71-stable before and it succesfully published one package, but have exited right after it because `stderr` was not empty Reviewed By: cortinico, cipolleschi Differential Revision: D42836212 fbshipit-source-id: 6f2a9a512121683268fe6aae6a187fccb8d9dfbc
…err (facebook#36004) Summary: Pull Request resolved: facebook#36004 Changelog: [Internal] This fixes CircleCI job, which is responsible for publishing bumped packages. We should not check for `stderr`, apparently `npm` uses it to store debug information: - npm/npm#118 (comment) So we've tried to use this on 0.71-stable before and it succesfully published one package, but have exited right after it because `stderr` was not empty Reviewed By: cortinico, cipolleschi Differential Revision: D42836212 fbshipit-source-id: 6f2a9a512121683268fe6aae6a187fccb8d9dfbc
Summary:
Changelog: [Internal]
This fixes CircleCI job, which is responsible for publishing bumped packages. We should not check for
stderr
, apparentlynpm
uses it to store debug information:So we've tried to use this on 0.71-stable before and it succesfully published one package, but have exited right after it because
stderr
was not emptyDifferential Revision: D42836212