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

Unexpected exit status when token is provided #229

Open
weynsee opened this issue Jun 29, 2018 · 5 comments
Open

Unexpected exit status when token is provided #229

weynsee opened this issue Jun 29, 2018 · 5 comments

Comments

@weynsee
Copy link

weynsee commented Jun 29, 2018

Do you want to request a feature or report a bug?
Report a possible bug

What is the current behavior?
When token is provided bundlesize still exits with 0 status even if the checks fail.

If the current behavior is a bug, please provide the steps to reproduce.

  • Create project with a failing bundlesize check
  • Integrate with CI and supply a token
  • Configure CI to run build with bundlesize

What is the expected behavior?
If CI uses exit status code to verify build status, then the build should fail, but currently it does not.

Please mention other relevant information.

  • node version: 8.9.4
  • npm version: 3.10.8
  • Operating system: N/A
  • bundlesize version: 0.17.0
  • CI you are using: TravisCI
@palashmon
Copy link
Collaborator

Hi, thanks for reporting this but this issue is not clear to me. Do you mean like your CI build failed but bundlesize still passed?

@weynsee
Copy link
Author

weynsee commented Jul 9, 2018

Actually the CI build passed even though bundlesize failed. When I run bundlesize and the bundle size exceeds the max limit, it exits with an exit status of 0 so the CI sees it as a successful build. This only happens when CI integration is enabled. Is this expected behaviour?

@palashmon
Copy link
Collaborator

cc @siddharthkp

@weynsee
Copy link
Author

weynsee commented Jul 12, 2018

I created a quick PR here to hopefully better illustrate the problem I'm encountering (and a possible bug fix). Feel free to close it if the current behaviour is expected, thanks!

@oliverviljamaa
Copy link

We are seeing similar behaviour.

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

No branches or pull requests

3 participants