Skip to content

Run benchmarks in test mode by default instead of excluding them (#56418)#56418

Open
rubennorte wants to merge 1 commit intofacebook:mainfrom
rubennorte:export-D100464314
Open

Run benchmarks in test mode by default instead of excluding them (#56418)#56418
rubennorte wants to merge 1 commit intofacebook:mainfrom
rubennorte:export-D100464314

Conversation

@rubennorte
Copy link
Copy Markdown
Contributor

@rubennorte rubennorte commented Apr 11, 2026

Summary:

Changelog: [internal]

D92150163 excluded benchmark tests by default when running yarn fantom without --benchmarks. This was incorrect because it means benchmarks could silently break without being caught.

This changes the behavior so:

  1. By default (without --benchmarks), benchmarks run in test mode (single iteration for correctness only), ensuring they do not break.
  2. With --benchmarks, benchmarks run in full benchmark mode (multiple iterations for performance measurement).

Also renames FANTOM_FORCE_TEST_MODE to FANTOM_RUN_BENCHMARKS and forceTestModeForBenchmarks to runBenchmarks to better reflect the intent (opt-in to full benchmarks rather than opt-in to test mode).

Differential Revision: D100464314

@meta-cla meta-cla 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 Apr 11, 2026
@meta-codesync
Copy link
Copy Markdown

meta-codesync bot commented Apr 11, 2026

@rubennorte has exported this pull request. If you are a Meta employee, you can view the originating Diff in D100464314.

@meta-codesync meta-codesync bot changed the title Run benchmarks in test mode by default instead of excluding them Run benchmarks in test mode by default instead of excluding them (#56418) Apr 11, 2026
rubennorte added a commit to rubennorte/react-native that referenced this pull request Apr 11, 2026
…ebook#56418)

Summary:

Changelog: [internal]

D92150163 excluded benchmark tests by default when running `yarn fantom` without `--benchmarks`. This was incorrect because it means benchmarks could silently break without being caught.

This changes the behavior so:
1. By default (without `--benchmarks`), benchmarks run in test mode (single iteration for correctness only), ensuring they do not break.
2. With `--benchmarks`, benchmarks run in full benchmark mode (multiple iterations for performance measurement).

Also renames `FANTOM_FORCE_TEST_MODE` to `FANTOM_RUN_BENCHMARKS` and `forceTestModeForBenchmarks` to `runBenchmarks` to better reflect the intent (opt-in to full benchmarks rather than opt-in to test mode).

Differential Revision: D100464314
…ebook#56418)

Summary:
Pull Request resolved: facebook#56418

Changelog: [internal]

D92150163 excluded benchmark tests by default when running `yarn fantom` without `--benchmarks`. This was incorrect because it means benchmarks could silently break without being caught.

This changes the behavior so:
1. By default (without `--benchmarks`), benchmarks run in test mode (single iteration for correctness only), ensuring they do not break.
2. With `--benchmarks`, benchmarks run in full benchmark mode (multiple iterations for performance measurement).

Also renames `FANTOM_FORCE_TEST_MODE` to `FANTOM_RUN_BENCHMARKS` and `forceTestModeForBenchmarks` to `runBenchmarks` to better reflect the intent (opt-in to full benchmarks rather than opt-in to test mode).

Differential Revision: D100464314
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. fb-exported meta-exported p: Facebook Partner: Facebook Partner

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant