Skip to content

Watcher backends: use Flow-typed object payloads #247

Watcher backends: use Flow-typed object payloads

Watcher backends: use Flow-typed object payloads #247

You are viewing an older attempt in the history of this workflow run. View latest attempt.
Triggered via pull request December 21, 2024 13:17
Status Failure
Total duration 5m 10s
Artifacts

build-test-and-deploy.yml

on: pull_request
Matrix: test
Type check, lint, smoke test
43s
Type check, lint, smoke test
Tests with coverage
1m 16s
Tests with coverage
Fit to window
Zoom out
Zoom in

Annotations

1 error and 7 warnings
test (ubuntu-latest, lts/*) / Tests [Node.js lts/*, ubuntu-latest, Using yarn.lock]
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test (ubuntu-latest, lts/-1) / Tests [Node.js lts/-1, ubuntu-latest, Using yarn.lock]
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Type check, lint, smoke test
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Type check, lint, smoke test: packages/metro-transform-plugins/src/addParamsToDefineCall.js#L26
Always use `== null` or `!= null` to check for `null` AND `undefined` values (even if you just expect either of them). Within fb we treat them as equal and `== null` checks for both
Tests with coverage
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636