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

[Circle CI] Fix buck failures on master #17295

Closed
wants to merge 11 commits into from

Conversation

hramos
Copy link
Contributor

@hramos hramos commented Dec 20, 2017

WIP.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Dec 20, 2017
We did not update the cache key when buck was downgraded to 09, and this prevents us from testing with the 11 version
@pull-bot
Copy link

pull-bot commented Dec 20, 2017

Fails
🚫

❔ This pull request needs a description.

Warnings
⚠️

📋 Test Plan - This PR appears to be missing a Test Plan.

⚠️

📋 Release Notes - This PR appears to be missing Release Notes.

@facebook-github-bot label Needs more information

@facebook-github-bot label Needs more information

@facebook-github-bot label Needs more information

Generated by 🚫 dangerJS

hramos and others added 9 commits December 20, 2017 14:38
No need to use branch in cache keys when checksum is used, ensures cache hits in PRs, forks when checksummed files have not changed
We were previously omitting BUCK defs from the cache key, which could result in new deps not being pulled. Also, separate out buck fetches so it is clear which step is being performed in Circle UI
Upon further inspection, this cache is not contributing much.
Fix flow issues
This has been recently added to Node 8.x. Since it makes our tests to fail, I decided to
do a workaround that works for all the versions. Submitted by @grabbou.
@pull-bot
Copy link

Fails
🚫

❔ This pull request needs a description.

Warnings
⚠️

📋 Test Plan - This PR appears to be missing a Test Plan.

⚠️

📋 Release Notes - This PR appears to be missing Release Notes.

@facebook-github-bot label Needs more information

@facebook-github-bot label Needs more information

@facebook-github-bot label Needs more information

Generated by 🚫 dangerJS

@facebook-github-bot facebook-github-bot added the Import Started This pull request has been imported. This does not imply the PR has been approved. label Dec 22, 2017
Copy link
Contributor

@facebook-github-bot facebook-github-bot left a comment

Choose a reason for hiding this comment

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

@hramos is landing this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@hramos
Copy link
Contributor Author

hramos commented Dec 22, 2017

Not 100% there yet but landing to clear out some already-resolved errors on master.

@hramos hramos deleted the buck-version branch December 22, 2017 20:47
mathiasbynens pushed a commit to mathiasbynens/react-native that referenced this pull request Jan 13, 2018
Summary:
WIP.
Closes facebook#17295

Differential Revision: D6628523

Pulled By: hramos

fbshipit-source-id: ac2833e99de9e94340b8027469cc74a5b7379962
grabbou pushed a commit to react-native-community/cli that referenced this pull request Sep 26, 2018
Summary:
WIP.
Closes facebook/react-native#17295

Differential Revision: D6628523

Pulled By: hramos

fbshipit-source-id: ac2833e99de9e94340b8027469cc74a5b7379962
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Import Started This pull request has been imported. This does not imply the PR has been approved.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants