Morph MORPH
SIGN IN SIGN UP
facebook / react-native UNCLAIMED

A framework for building native applications using React

0 0 29 C++
Normal View History Raw
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
/**
Update copyright headers from Facebook to Meta Reviewed By: aaronabramov Differential Revision: D33367752 fbshipit-source-id: 4ce94d184485e5ee0a62cf67ad2d3ba16e285c8f
2021-12-30 15:08:43 -08:00
* Copyright (c) Meta Platforms, Inc. and affiliates.
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
*
* This source code is licensed under the MIT license found in the
* LICENSE file in the root directory of this source tree.
*
* @format
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
* @flow strict-local
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
*/
'use strict';
/**
* This script runs JavaScript tests.
* Available arguments:
* --maxWorkers [num] - how many workers, default 1
* --jestBinary [path] - path to jest binary, defaults to local node modules
* --yarnBinary [path] - path to yarn binary, defaults to yarn
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
* --flowBinary [path] - path to flow binary, defaults to running `yarn run flow-check`
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
*/
Replace shelljs in run-ci-javascript-tests.js (#52095) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52095 This diff removes `shelljs` from `run-ci-javascript-tests.js` and replaces `echo, exec, and exit` methods. ### Motivation Decrease number of references to `shelljs` across the react-native-github. Changelog: [Internal] Reviewed By: NickGerleman Differential Revision: D76512374 fbshipit-source-id: 6e02901b570cf9a36bd13a075106a7066a85a2d9
2025-06-23 09:39:44 -07:00
const {execSync} = require('child_process');
Update prettier-plugin-hermes-parser in fbsource to 0.31.1 (#52996) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52996 Bump prettier-plugin-hermes-parser to 0.31.1. Changelog: [internal] Reviewed By: pieterv Differential Revision: D79481936 fbshipit-source-id: 4decd5c92722f935a6a03b6d2205bc31b864fb5d
2025-08-01 20:18:36 -07:00
const argv /*:$ReadOnly<{
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
maxWorkers?: number,
jestBinary?: string,
flowBinary?: string,
yarnBinary?: string,
Update prettier-plugin-hermes-parser in fbsource to 0.31.1 (#52996) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52996 Bump prettier-plugin-hermes-parser to 0.31.1. Changelog: [internal] Reviewed By: pieterv Differential Revision: D79481936 fbshipit-source-id: 4decd5c92722f935a6a03b6d2205bc31b864fb5d
2025-08-01 20:18:36 -07:00
}> */ =
Migrate to suppression with error code in xplat: 1/n (#53439) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/53439 Changelog: [Internal] Reviewed By: panagosg7 Differential Revision: D80809220 fbshipit-source-id: 6f432d8302934b9fee9780ac1d6ba6c87c0b3899
2025-08-22 10:35:39 -07:00
// $FlowFixMe[incompatible-type]
// $FlowFixMe[incompatible-exact]
// $FlowFixMe[incompatible-indexer]
Update prettier-plugin-hermes-parser in fbsource to 0.31.1 (#52996) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52996 Bump prettier-plugin-hermes-parser to 0.31.1. Changelog: [internal] Reviewed By: pieterv Differential Revision: D79481936 fbshipit-source-id: 4decd5c92722f935a6a03b6d2205bc31b864fb5d
2025-08-01 20:18:36 -07:00
require('yargs').argv;
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
const numberOfMaxWorkers = argv.maxWorkers ?? 1;
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
const JEST_BINARY = argv.jestBinary ?? './node_modules/.bin/jest';
RNCI: Migrate OSS CI to Flow DotSlash Binary (#50743) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/50743 Expose `--flowBinary` on React Native CI script. Changelog: [Internal] Reviewed By: SamChou19815 Differential Revision: D73062734 fbshipit-source-id: 6501b6ff2976e4e7e0bbc1c6025205cde4169679
2025-04-15 16:09:45 -07:00
const FLOW_BINARY = argv.flowBinary;
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
const YARN_BINARY = argv.yarnBinary ?? 'yarn';
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
class ExecError extends Error {
constructor(cause /*: Error */) {
super(cause.message, {cause});
this.name = 'ExecError';
}
}
function describe(message /*: string */) {
Replace shelljs in run-ci-javascript-tests.js (#52095) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52095 This diff removes `shelljs` from `run-ci-javascript-tests.js` and replaces `echo, exec, and exit` methods. ### Motivation Decrease number of references to `shelljs` across the react-native-github. Changelog: [Internal] Reviewed By: NickGerleman Differential Revision: D76512374 fbshipit-source-id: 6e02901b570cf9a36bd13a075106a7066a85a2d9
2025-06-23 09:39:44 -07:00
console.log(`\n\n>>>>> ${message}\n\n\n`);
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
}
try {
Replace shelljs in run-ci-javascript-tests.js (#52095) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52095 This diff removes `shelljs` from `run-ci-javascript-tests.js` and replaces `echo, exec, and exit` methods. ### Motivation Decrease number of references to `shelljs` across the react-native-github. Changelog: [Internal] Reviewed By: NickGerleman Differential Revision: D76512374 fbshipit-source-id: 6e02901b570cf9a36bd13a075106a7066a85a2d9
2025-06-23 09:39:44 -07:00
console.log('Executing JavaScript tests');
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
Implement new feature flag system (re-land) (#42678) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/42678 Changelog: [internal] This is a re-application of https://github.com/facebook/react-native/pull/42430, which had to be reverted because of crashes in optimized builds on Android: ``` Abort Reason: terminating due to uncaught exception of type facebook::jni::JniException: java.lang.ClassNotFoundException: com.facebook.react.internal.featureflags.ReactNativeFeatureFlagsProvider ``` The root cause of that was that that class was removed because it wasn't statically referenced from Kotlin/Java, but it was dynamically referenced from C++ (in `ReactNativeFeatureFlagsProviderHolder.cpp`). This applies the same changes + adds `DoNotStrip` annotations for the affected class and all its methods. Reviewed By: huntie Differential Revision: D53122992 fbshipit-source-id: efc4d5636a3f2d39b86e9c098bff408b6688b80b
2024-01-26 09:55:27 -08:00
describe('Test: feature flags codegen');
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
execAndLog(`${YARN_BINARY} run featureflags --verify-unchanged`);
Remove build package.json dirty state check (#55420) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/55420 After https://github.com/facebook/react-native/pull/54857 (use of the "publishConfig" field), this check is no longer necessary, since `yarn build` will no longer make changes to any checked in files. In the (expectedly) rare case that `yarn build --prepack` changes are committed (only intended for CI), Flow will also fail independently. Changelog: [Internal] Reviewed By: cipolleschi Differential Revision: D92397786 fbshipit-source-id: 872cc91b62295cdb6d8c2799cffb8a4cadc4106e
2026-02-05 09:14:33 -08:00
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
describe('Test: eslint');
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
execAndLog(`${YARN_BINARY} run lint`);
ci: verify JS build artifacts aren't committed (#48091) Summary: Building our JS packages dirties the repo. This makes sure we don't accidentally commit these to the repo, as it'll break Flow tests with an obscure error message. Changelog: [Internal] Pull Request resolved: https://github.com/facebook/react-native/pull/48091 Test Plan: Ran this locally, the GH lint action should run on this PR. I'll intentionally add a build artifact to validate. | A | B | C | | - | - | - | | ![CleanShot 2024-12-04 at 14 11 16@2x](https://github.com/user-attachments/assets/11c05c32-12c8-4d85-9a28-b3bdffb42ea0) | ![CleanShot 2024-12-04 at 14 11 22@2x](https://github.com/user-attachments/assets/b4c4f1dc-2cb9-4138-8931-13e71c015a6d) | ![CleanShot 2024-12-04 at 14 19 31@2x](https://github.com/user-attachments/assets/953bf783-57ba-4832-bbd8-b36e23a2ccb4) | Reviewed By: cipolleschi Differential Revision: D66760144 Pulled By: blakef fbshipit-source-id: 81f20fa0a83d5f17b5773d1608664b683ba74409
2024-12-06 13:21:23 -08:00
Validate RN JS API snapshot on CI (#52352) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52352 This diff adds excution of `yarn build-types --validate` to run RN JS API snapshot validation on CI. ### Motivation Detect react-native public API changes before they land. Changelog: [Internal] Reviewed By: huntie Differential Revision: D76340729 fbshipit-source-id: 10c465418e0ba4eb05cf557a16119f9756843d9e
2025-07-01 08:58:15 -07:00
describe('Test: Validate JS API snapshot');
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
execAndLog(`${YARN_BINARY} run build-types --validate`);
Validate RN JS API snapshot on CI (#52352) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52352 This diff adds excution of `yarn build-types --validate` to run RN JS API snapshot validation on CI. ### Motivation Detect react-native public API changes before they land. Changelog: [Internal] Reviewed By: huntie Differential Revision: D76340729 fbshipit-source-id: 10c465418e0ba4eb05cf557a16119f9756843d9e
2025-07-01 08:58:15 -07:00
Remove CI check jobs on .flowconfig.android in react-native (#39158) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/39158 .flowconfig.android is the same as .flowconfig now. The check is meaningless. This diff removes it and the flowconfig. Changelog: [Internal] Reviewed By: yungsters Differential Revision: D48629137 fbshipit-source-id: bc1bee9426eed7bc41dc7a1efe75333e1191e066
2023-08-26 10:00:22 -07:00
describe('Test: Flow check');
RNCI: Migrate OSS CI to Flow DotSlash Binary (#50743) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/50743 Expose `--flowBinary` on React Native CI script. Changelog: [Internal] Reviewed By: SamChou19815 Differential Revision: D73062734 fbshipit-source-id: 6501b6ff2976e4e7e0bbc1c6025205cde4169679
2025-04-15 16:09:45 -07:00
const flowCommand =
FLOW_BINARY == null
? `${YARN_BINARY} run flow-check`
make run-ci-javascript-tests.js use `flow full-check` (#54883) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/54883 `flow full-check` has been available since Flow v0.292.0 Changelog: [Internal] Reviewed By: SamChou19815 Differential Revision: D89097999 fbshipit-source-id: a4e7de0cfe4ac9c52eb067f06b127fb3f3efd0b9
2025-12-15 15:41:33 -08:00
: `${FLOW_BINARY} full-check`;
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
execAndLog(flowCommand);
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
Add `@react-native/codegen-typescript-test` to verify .d.ts files in `@react-native/codegen` (1) (#36562) Summary: - Add a typescript project to test `CodegenSchema.d.ts`. More tests for other .d.ts files will be added in future pull requests. - The build script scans all snapshots from `react-native/codegen`'s typescript frontend and generates .ts files for each snapshot, but they are .gitignore-ed. - `npm run build` will build these .ts files against `CodegenSchema.d.ts` after generating them. - A failed jest case is included to ensure CI catch it, it will be removed before merged. bypass-github-export-checks ## Changelog: [General] [Added] - Add react-native/codegen-typescript-test to verify .d.ts files in react-native/codegen (1) Pull Request resolved: https://github.com/facebook/react-native/pull/36562 Test Plan: `npm run build` in `packages/react-native-codegen-typescript-test` and see all test files appear in `__generated__`. ## Screenshot ![Untitled](https://user-images.githubusercontent.com/53799235/226757755-cab4cb29-7d22-46a1-9ecb-d6732122ed38.png) Reviewed By: rshest Differential Revision: D44292277 Pulled By: cipolleschi fbshipit-source-id: 8d79fe913f9563d64c92aae7c4f4e97a24ae9a21
2023-04-05 07:38:25 -07:00
/*
Revert D49370200: Migrate codegen to shared build setup, remove package build pre-step from RNTester Differential Revision: D49370200 Original commit changeset: 992913155169 Original Phabricator Diff: D49370200 fbshipit-source-id: e8232c97c22065fb54ac940ee2351b2155eb51e0
2023-10-23 12:00:54 -07:00
* Build @react-native/codegen and @react-native/codegen-typescript-test
Add `@react-native/codegen-typescript-test` to verify .d.ts files in `@react-native/codegen` (1) (#36562) Summary: - Add a typescript project to test `CodegenSchema.d.ts`. More tests for other .d.ts files will be added in future pull requests. - The build script scans all snapshots from `react-native/codegen`'s typescript frontend and generates .ts files for each snapshot, but they are .gitignore-ed. - `npm run build` will build these .ts files against `CodegenSchema.d.ts` after generating them. - A failed jest case is included to ensure CI catch it, it will be removed before merged. bypass-github-export-checks ## Changelog: [General] [Added] - Add react-native/codegen-typescript-test to verify .d.ts files in react-native/codegen (1) Pull Request resolved: https://github.com/facebook/react-native/pull/36562 Test Plan: `npm run build` in `packages/react-native-codegen-typescript-test` and see all test files appear in `__generated__`. ## Screenshot ![Untitled](https://user-images.githubusercontent.com/53799235/226757755-cab4cb29-7d22-46a1-9ecb-d6732122ed38.png) Reviewed By: rshest Differential Revision: D44292277 Pulled By: cipolleschi fbshipit-source-id: 8d79fe913f9563d64c92aae7c4f4e97a24ae9a21
2023-04-05 07:38:25 -07:00
*
* The typescript-test project use TypeScript to write test cases
* In order to make these tests discoverable to jest
* *-test.ts must be compiled to *-test.js before running jest
*/
Revert D49370200: Migrate codegen to shared build setup, remove package build pre-step from RNTester Differential Revision: D49370200 Original commit changeset: 992913155169 Original Phabricator Diff: D49370200 fbshipit-source-id: e8232c97c22065fb54ac940ee2351b2155eb51e0
2023-10-23 12:00:54 -07:00
describe('Test: Build @react-native/codegen');
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
execAndLog(`${YARN_BINARY} --cwd ./packages/react-native-codegen run build`);
Add `@react-native/codegen-typescript-test` to verify .d.ts files in `@react-native/codegen` (1) (#36562) Summary: - Add a typescript project to test `CodegenSchema.d.ts`. More tests for other .d.ts files will be added in future pull requests. - The build script scans all snapshots from `react-native/codegen`'s typescript frontend and generates .ts files for each snapshot, but they are .gitignore-ed. - `npm run build` will build these .ts files against `CodegenSchema.d.ts` after generating them. - A failed jest case is included to ensure CI catch it, it will be removed before merged. bypass-github-export-checks ## Changelog: [General] [Added] - Add react-native/codegen-typescript-test to verify .d.ts files in react-native/codegen (1) Pull Request resolved: https://github.com/facebook/react-native/pull/36562 Test Plan: `npm run build` in `packages/react-native-codegen-typescript-test` and see all test files appear in `__generated__`. ## Screenshot ![Untitled](https://user-images.githubusercontent.com/53799235/226757755-cab4cb29-7d22-46a1-9ecb-d6732122ed38.png) Reviewed By: rshest Differential Revision: D44292277 Pulled By: cipolleschi fbshipit-source-id: 8d79fe913f9563d64c92aae7c4f4e97a24ae9a21
2023-04-05 07:38:25 -07:00
describe('Test: Build @react-native/codegen-typescript-test');
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
execAndLog(
`${YARN_BINARY} --cwd ./private/react-native-codegen-typescript-test run build`,
);
Add `@react-native/codegen-typescript-test` to verify .d.ts files in `@react-native/codegen` (1) (#36562) Summary: - Add a typescript project to test `CodegenSchema.d.ts`. More tests for other .d.ts files will be added in future pull requests. - The build script scans all snapshots from `react-native/codegen`'s typescript frontend and generates .ts files for each snapshot, but they are .gitignore-ed. - `npm run build` will build these .ts files against `CodegenSchema.d.ts` after generating them. - A failed jest case is included to ensure CI catch it, it will be removed before merged. bypass-github-export-checks ## Changelog: [General] [Added] - Add react-native/codegen-typescript-test to verify .d.ts files in react-native/codegen (1) Pull Request resolved: https://github.com/facebook/react-native/pull/36562 Test Plan: `npm run build` in `packages/react-native-codegen-typescript-test` and see all test files appear in `__generated__`. ## Screenshot ![Untitled](https://user-images.githubusercontent.com/53799235/226757755-cab4cb29-7d22-46a1-9ecb-d6732122ed38.png) Reviewed By: rshest Differential Revision: D44292277 Pulled By: cipolleschi fbshipit-source-id: 8d79fe913f9563d64c92aae7c4f4e97a24ae9a21
2023-04-05 07:38:25 -07:00
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
describe('Test: Jest');
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
execAndLog(
`${JEST_BINARY} --maxWorkers=${numberOfMaxWorkers} --ci --reporters="default" --reporters="jest-junit"`,
);
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
Fix Errors with TypeScript Tests Summary: This fixes some style errors found by dtslint, along with some test cases for StyleSheet.compose() where the recent change made it slightly too permissive when explicit return types are given. I also added runs of the TS tests to a script which runs in sandcastle so we can catch this at diff-submission time in the future. Changelog: [General][Fixed] - Fix Errors with TypeScript Tests Reviewed By: lunaleaps Differential Revision: D42085257 fbshipit-source-id: 7e6ca49d3c3aef822c61c97ecc07b55b0a949d51
2022-12-15 19:17:58 -08:00
describe('Test: TypeScript tests');
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
execAndLog(`${YARN_BINARY} run test-typescript`);
} catch (e) {
if (e instanceof ExecError) {
console.error(e.message);
process.exitCode = 1;
} else {
throw e;
Fix Errors with TypeScript Tests Summary: This fixes some style errors found by dtslint, along with some test cases for StyleSheet.compose() where the recent change made it slightly too permissive when explicit return types are given. I also added runs of the TS tests to a script which runs in sandcastle so we can catch this at diff-submission time in the future. Changelog: [General][Fixed] - Fix Errors with TypeScript Tests Reviewed By: lunaleaps Differential Revision: D42085257 fbshipit-source-id: 7e6ca49d3c3aef822c61c97ecc07b55b0a949d51
2022-12-15 19:17:58 -08:00
}
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
} finally {
Replace shelljs in run-ci-javascript-tests.js (#52095) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52095 This diff removes `shelljs` from `run-ci-javascript-tests.js` and replaces `echo, exec, and exit` methods. ### Motivation Decrease number of references to `shelljs` across the react-native-github. Changelog: [Internal] Reviewed By: NickGerleman Differential Revision: D76512374 fbshipit-source-id: 6e02901b570cf9a36bd13a075106a7066a85a2d9
2025-06-23 09:39:44 -07:00
console.log('Finished.');
Run the same JavaScript test script in Sandcastle and Circle (#24422) Summary: Consolidate JavaScript tests from open source into a single script that can be executed by both Circle CI and Sandcastle, the internal Facebook CI. [General] [Changed] - Switch internal and external CI to use the same script when running JavaScript tests Pull Request resolved: https://github.com/facebook/react-native/pull/24422 Reviewed By: cpojer Differential Revision: D14895773 fbshipit-source-id: d428929cc4e5219e02f5920259e08e0b3d24874c
2019-04-12 09:50:13 -07:00
}
Fix run-ci-javascript-tests script (#52364) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/52364 Changelog: [Internal] D76512374 broke error reporting in `run-ci-javascript-tests.js`. This is partly because the file was untyped and we missed that the `.code` check on the result of `execSync` was always going to be falsy. Also, `execSync`'s default error handling mechanism is not human-friendly - it throws an `Error` with `Buffer`s for stdout and stderr (see [example](https://github.com/facebook/react-native/actions/runs/16003656383/job/45144825919?pr=52357&fbclid=IwY2xjawLRyfpleHRuA2FlbQIxMQBicmlkETFZSG1xeWhTWWczR1paS0lKAR4pF46Z-J2CbSk7YdHZJ-N3F9eQJ7hR4EowfLV6mUtzMLg8j-EWdZiGY1la6A_aem_1Zbvn6fD5NS9YO-B7QJssg)). Here, I'm adding types, removing dead code and preserving stdout and stderr from all child processes in a human-readable format. Reviewed By: huntie Differential Revision: D77648312 fbshipit-source-id: c6d98e668d6edf15729fa02fecb3408b9dd6debc
2025-07-02 03:09:18 -07:00
function execAndLog(command /*: string */) {
console.log(`Executing: ${command}`);
try {
execSync(command, {
stdio: ['ignore', 'inherit', 'inherit'],
encoding: 'utf8',
});
} catch (e) {
throw new ExecError(e);
}
}
Reference in New Issue Copy Permalink