Repository navigation
Run the web elements test as a unit test, so the Publish tests pass on the packed packages - #112
Merged
Merged
Conversation
Jest matches the integration test pattern without regard to case, so the word Integration in webIntegrationElements.test.js put this unit test of PipelineBuilder among the integration tests. The Publish workflow runs those against the packed packages, where the core package no longer holds tests/configTestFlowElement.js, which the test's configuration names, so the test failed there on every runner.
jwrosewell
marked this pull request as ready for review
November 14, 2026 10:36
This was referenced Nov 14, 2026
Regenerate the TypeScript types, and make every package's types compile for a TypeScript caller
#113
Merged
Draft
This file contains hidden or 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
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.
Problem
The Nightly Pipeline dry run 43578169805, on a throwaway branch holding
rcat 7539a0b with the drafts then approved merged in, fails one test in all eight Test jobs of its Publish stage, being Ubuntu, Ubuntu ARM, Windows and macOS on Node.js 22 and 24.The test came with #105 and builds a Pipeline from
tests/config.json, which names its element./tests/configTestFlowElement.js.PipelineBuilder.buildFromConfigurationrequires that name from the core package's own folder (pipelineBuilder.jslines 136 to 151 at a9a3bd2e). In this repository that folder holdstests. The Publish stage runs its tests against the packed packages, and since #106 the core package packs notestsfolder.The test is a unit test, and it ran against the packed packages because of its name. The
integration-testscript picks tests with--testPathPattern="(examples/|integration|location/)"(package.jsonline 26 at a9a3bd2e). Jest matches that pattern ignoring case (testPathPatternToRegExp.tsline 16 at Jest 29.7.0), sowebIntegrationElementsmatched. Theunit-testscript leaves outintegrationwith--testPathIgnorePatterns, which Jest matches with case (SearchSource.tslines 82 to 89 at Jest 29.7.0), so the test ran in both sets.Monday's Publish run would fail the same way, before it publishes anything. The Publish dry run of the same branch, 43578220634, did not show it, because it skipped the tests that the nightly ran.
What changed
pipeline/fiftyone.pipeline.core/tests/webIntegrationElements.test.jsis renamedwebElements.test.js, with no change to its content. It now runs only among the unit tests, which run in this repository, where the core package's folder holdstests.core.test.jsreads the sameconfig.json, and its name has never matched the integration pattern.Tests
rchas it.version/node-monday-composite2, being the nightly's branch with this change and a throwaway commit that leaves out macOS and skips the performance comparison, with the tests run. All six Test jobs, Ubuntu, Ubuntu ARM and Windows on Node.js 22 and 24, ran the integration tests against the packed packages and passed 109 with 4 skipped, of 113. The nightly ran 168 there, and the renamed file holds the other 55. Package then dry-published all 16 packages at 4.5.103.Full build
Run 43580463887 on
tmp/pr-matrix-112, started bytools/pr-matrix.pywithout macOS. All 7Setting 'PullRequestSha'lines give this head, a195c31, and Configure printed "Left out 2 macOS entries". Each of the six Build and Test jobs, Ubuntu, Ubuntu ARM and Windows on Node.js 22 and 24, passed 1,486 unit tests with 2 skipped and 96 integration tests with 4 skipped, andwebElements.test.jspassed among the unit tests.macOS was left out of this draft's full build under the 9 November decision. The nightly above ran the same test on macOS, where it failed only for the reason above. The rc head is built with macOS before it merges into main.
What remains
Nothing for this change.