Conversation
On the x86_64-windows target `.#unit-tests` cross-builds the tests with a manifest for logos-windows-ci instead of running them (logos-module-builder #260). Says how a module opts in, and that external libraries must be mocked there for now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
📊 Tutorial execution reportsRendered tutorial alongside the commands actually run and their output (updated each run, commit
Pages can take a minute to update after the run finishes. |
This branch has not been deployed
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
1 participant
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.
The developer guide's table of module outputs says every output also exists for the
x86_64-windowscross target. With logos-module-builder #260,.#unit-testsdoes, but it behaves differently there: it cross-builds the test executables and writes a manifest (share/logos-tests/<module>.json) that logos-windows-ci runs on a Windows runner, instead of running them. This adds that paragraph, how a module opts in (targets: default unit-tests,tests: true), and that a real shared external library has to be mocked withtests.mockCLibson Windows for now.Merge after #260: on the builder's master,
packages.x86_64-windows.unit-testsdoes not evaluate. logos-capability-module #32 and logos-verified-proxy-module #15 are the first modules to opt in.🤖 Generated with Claude Code