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

Don't reset error codes on CI build #11655

Merged
merged 2 commits into from
Nov 25, 2017
Merged

Don't reset error codes on CI build #11655

merged 2 commits into from
Nov 25, 2017

Conversation

gaearon
Copy link
Collaborator

@gaearon gaearon commented Nov 25, 2017

I think this was added in #8486 but if I'm not mistaken it causes issues after my changes in #11633.

Specifically, prod tests on bundles now run after build and actually depend on the up-to-date error code file being available. Otherwise any newly added invariants can't be "decoded", as they're not in the committed error code file.

I noticed this in #11652. Will see if the same fix there works. If it does, I'll merge this.

@gaearon
Copy link
Collaborator Author

gaearon commented Nov 25, 2017

yeah that works

@gaearon gaearon merged commit d235e61 into master Nov 25, 2017
@gaearon gaearon deleted the gaearon-patch-2 branch November 25, 2017 02:23
HeroProtagonist pushed a commit to HeroProtagonist/react that referenced this pull request Nov 26, 2017
* Don't reset error codes on CI build

* Add an explanation
raphamorim pushed a commit to raphamorim/react that referenced this pull request Nov 27, 2017
* Don't reset error codes on CI build

* Add an explanation
Ethan-Arrowood pushed a commit to Ethan-Arrowood/react that referenced this pull request Dec 8, 2017
* Don't reset error codes on CI build

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

Successfully merging this pull request may close these issues.

2 participants