Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
36758
d88d853f chore(misc): rerun watch e2e (flake sample 4) No code change. Sampling the suite after the batch-union fix to see whether the flake rate actually moved. Also checks that an empty commit produces a real e2e run rather than a cache replay.
by Craigory C...
Failed
36758
d88d853f chore(misc): rerun watch e2e (flake sample 4) No code change. Sampling the suite after the batch-union fix to see whether the flake rate actually moved. Also checks that an empty commit produces a real e2e run rather than a cache replay.
by Craigory C...
Succeeded
36758
c4bbaaff fix(misc): assert watched file changes across batches, not within one CI failure on 4a8bdbb0 (e2e-nx watch.test.ts, "should watch for global workspace file changes"). The watcher reported all four files, split across three batches: libs/<p1>/newfile.txt libs/<p2>/newfile.txt libs/<p1>/newfile2.txt newfile2.txt The writes are 10ms apart and the watcher coalesces on a 100ms idle window, so a single batch is a property of an idle machine, not an invariant. That run's per-test times were 10-26s against 6-7s on the green run before it. The pre-existing assertion had the same assumption -- it read output[0] -- so this is a latent flake the rewrite carried forward rather than a new one. Assert the union across batches instead. The negative assertions survive: a global file leaking into a project-scoped run still breaks equality. Also stop reporting a timeout as an early exit. `exited` was read after our own treeKill, so every timeout claimed "nx watch exited before producing the expected output". Sample it before the kill. Contrary to the hypothesis this branch started from, the daemon watcher was alive and reporting throughout -- no inotify exhaustion. The watcher-failure plumbing in bc2cffe68 stands on its own as a real bug, but it is not what makes this suite flaky.
by Craigory C...
Failed
36758
4a8bdbb0 chore(misc): correct the close-listener comment in the watch e2e The old code used `on('close')`, not `once`; the hazard is adding any listener after the event already fired.
by Craigory C...
Succeeded
36758
c1362e68 chore(misc): de-flake the nx watch e2e suite Same source tree produced one failure in one CI run and four in the next, every failure shaped as `Received: []` or a TypeError on an empty output array. Two harness defects, both measured against a fixture workspace driving real `nx watch`: - `runWatch` never re-added NX_PROJECT_GRAPH_CACHE_DIRECTORY, which getStrippedEnvironmentVariables drops, while beforeAll, runWatchWithReconnect and the afterEach log dump all did. Seven of the eight tests ran against a different daemon than the one whose log CI printed, and a second daemon watched the same workspace for the whole suite. - `getOutput()` slept a flat 1000ms and then looked once. Happy-path latency measures 100-116ms (the native watcher's IDLE_WINDOW), so the window had ~10x headroom, but any excursion past it became an unreadable empty array. Waiting for the expected output instead of a fixed window keeps a silent watcher failing while letting a slow one pass. The 500ms settle after the match preserves the suite's negative assertions -- several tests also assert that unwatched projects did NOT run, which an early return would have silently stopped checking.
by Craigory C...
Canceled
36758
c1362e68 chore(misc): de-flake the nx watch e2e suite Same source tree produced one failure in one CI run and four in the next, every failure shaped as `Received: []` or a TypeError on an empty output array. Two harness defects, both measured against a fixture workspace driving real `nx watch`: - `runWatch` never re-added NX_PROJECT_GRAPH_CACHE_DIRECTORY, which getStrippedEnvironmentVariables drops, while beforeAll, runWatchWithReconnect and the afterEach log dump all did. Seven of the eight tests ran against a different daemon than the one whose log CI printed, and a second daemon watched the same workspace for the whole suite. - `getOutput()` slept a flat 1000ms and then looked once. Happy-path latency measures 100-116ms (the native watcher's IDLE_WINDOW), so the window had ~10x headroom, but any excursion past it became an unreadable empty array. Waiting for the expected output instead of a fixed window keeps a silent watcher failing while letting a slow one pass. The 500ms settle after the match preserves the suite's negative assertions -- several tests also assert that unwatched projects did NOT run, which an early return would have silently stopped checking.
by Craigory C...
Canceled
36758
c1362e68 chore(misc): de-flake the nx watch e2e suite Same source tree produced one failure in one CI run and four in the next, every failure shaped as `Received: []` or a TypeError on an empty output array. Two harness defects, both measured against a fixture workspace driving real `nx watch`: - `runWatch` never re-added NX_PROJECT_GRAPH_CACHE_DIRECTORY, which getStrippedEnvironmentVariables drops, while beforeAll, runWatchWithReconnect and the afterEach log dump all did. Seven of the eight tests ran against a different daemon than the one whose log CI printed, and a second daemon watched the same workspace for the whole suite. - `getOutput()` slept a flat 1000ms and then looked once. Happy-path latency measures 100-116ms (the native watcher's IDLE_WINDOW), so the window had ~10x headroom, but any excursion past it became an unreadable empty array. Waiting for the expected output instead of a fixed window keeps a silent watcher failing while letting a slow one pass. The 500ms settle after the match preserves the suite's negative assertions -- several tests also assert that unwatched projects did NOT run, which an early return would have silently stopped checking.
by Craigory C...
Failed
36758
Flaky task→
c1362e68 chore(misc): de-flake the nx watch e2e suite Same source tree produced one failure in one CI run and four in the next, every failure shaped as `Received: []` or a TypeError on an empty output array. Two harness defects, both measured against a fixture workspace driving real `nx watch`: - `runWatch` never re-added NX_PROJECT_GRAPH_CACHE_DIRECTORY, which getStrippedEnvironmentVariables drops, while beforeAll, runWatchWithReconnect and the afterEach log dump all did. Seven of the eight tests ran against a different daemon than the one whose log CI printed, and a second daemon watched the same workspace for the whole suite. - `getOutput()` slept a flat 1000ms and then looked once. Happy-path latency measures 100-116ms (the native watcher's IDLE_WINDOW), so the window had ~10x headroom, but any excursion past it became an unreadable empty array. Waiting for the expected output instead of a fixed window keeps a silent watcher failing while letting a slow one pass. The 500ms settle after the match preserves the suite's negative assertions -- several tests also assert that unwatched projects did NOT run, which an early return would have silently stopped checking.
by Craigory C...