fix(web): patch up worker build to provide artifacts for its tests #12082
Conversation
This file contains 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
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
mcdurdin
approved these changes
Aug 2, 2024
|
Changes in this pull request will be available for download in Keyman version 18.0.83-alpha |
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.
Ran into a scenario just earlier where
$KEYMAN_ROOT/common/web/lm-worker/build.sh clean build testwould fail becausetscwas never used to actually build the project's files; the tests would report that certain imports from compiled source files were missing. (The lm-worker currently does not provide a 'test-index', instead providing import maps to each source's compiled form.)The only reason that our CI builds didn't fail is that
./common/predictive-textbuilt a project with a reference to the lm-worker project, and that triggered the build that lets the associated tests pass.@keymanapp-test-bot skip