feat: add wasmer-argus #4506
Merged
feat: add wasmer-argus #4506
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
BREAKING CHANGE: The `run` flag will no longer be available, as at this moment there is no utility for it in the general case. #
theduke
reviewed
Mar 21, 2024
syrusakbary
approved these changes
Mar 21, 2024
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.
Description
wasmer-argusis a test runner. It fetches packages from a user-defined WebContainer registry using its graphql endpoints: by default, this endpoint ishttp://registry.wasmer.io/graphql. Internally, it uses thewasmer-apicrate, therefore the target registry must be compatible with the queries defined in that crate.Since registries, to fetch every package in them, might need an authorization token,
wasmer-argushas support for user-defined tokens, which can be gathered automatically from the environment using theWASMER_TOKENvariable or from the CLI arguments with a dedicated flag.I tried to make the testing process as parallelised as possible.
wasmer-argusgathers informations about the available parallelism in the host machine usingstd::thread::available_parallelism; the user can, however, specify "the amount of parallelism" desired -- which controls the number of concurrent tests -- using another dedicated CLI flag.Further documentation can be found in the
README.md.Further steps
--helpis already quite explainatory)