forked from facebook/react-native
-
Notifications
You must be signed in to change notification settings - Fork 138
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
re-enable tests for testing #1106
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kelset
force-pushed
the
kelset/fix-circleci-e2e-test
branch
from
March 29, 2022 11:54
49a09e7
to
eb54e19
Compare
Summary: Changelog: [Internal] Copy over universal (across dry-run, nightly, release) work in `bump-oss-version` script This work is part of an effort to automate the release process by using a push to a release branch as a trigger to prepare, package and deploy react-native to npm from CircleCI The following diagram describes the context (what kind of releases we do, relevant scripts and what they do), the pre-existing process for the different types of release and how I've modified the process. {F683387103} This diff creates the `set-rn-version` script referenced by extracting it out of `bump-oss-version` Reviewed By: sota000 Differential Revision: D32556608 fbshipit-source-id: 6c2868c01ddd930375279a5105bcd0d447f65734
Summary: Changelog: [Internal] Remove un-necessary package installs which was using `npm install flow-bin --save-dev` which was wiping out our `node_modules` from the circleCI yarn install. It was un-necessary as we already have `flow-bin` as a dependency in our current set-up. In addtion, we were running `npm pack` without properly copying over our package.json dependencies (which occurs in `prepare-package-for-release`) for a consumable react-native package. This may not have caused issue but technically we were creating an "incomplete" package to do our e2e testing on. Reviewed By: charlesbdudley Differential Revision: D33197965 fbshipit-source-id: 6583ef1f8e17333c0f27ecc37635c36ae5a0bb62
Summary: Changelog: [Internal] - Clean up - Remove `eslint-disable no-undef` by not requiring `shelljs/global` Reviewed By: cortinico Differential Revision: D33197964 fbshipit-source-id: 2e36fc10bf4e3230b8ae914f48d244446da43973
Summary: The CI is currently failing with: ``` Error extracting tarball /tmp/cache1419328940 : tar: root/.cache/yarn: Cannot mkdir: Permission denied tar: root/.cache/yarn/v6 ``` The problem is that we're sharing the Yarn cache between two jobs (`test_js` and `test_ios_unit_jsc`) which are executed on two difference executors (a Machine vs a Docker container). I've update the cache key to be `v5-yarn-cache-{{ .Environment.CIRCLE_JOB }}-{{ arch }}-{{ checksum "yarn.lock" }}` so the job name is accounted when computing the Cache Key. Moreover the `test_js` test was also failing on `flow check` as one of the library we depend on (`resolve`) added a test with a malformed JSON. I'm fixing this failure as well so the CI is back green. ## Changelog [Internal] - Updating Yarn Cache path to fix broken CI Pull Request resolved: facebook#32834 Test Plan: Verified that the external CI is green: facebook#32834 Reviewed By: lunaleaps Differential Revision: D33453702 Pulled By: cortinico fbshipit-source-id: 52bf42db583eaf6aa913f1bb164566f8c3563d36
(did the investigation, see updated comment in here #949) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
testing for CI
Please select one of the following
Summary
Related links from around:
Related commits from upstream:
Changelog
[CATEGORY] [TYPE] - Message
Test Plan