fix: only build xtask once for the tests

[Natoandro]

Use the xtask binary to run the tests.

• The change comes with new or modified tests
• Hard-to-understand functions have explanatory comments
• End-user documentation is updated to reflect the change

Summary by CodeRabbit

• New Features

  • Updated platform compatibility to x86_64-linux.
  • Added new configuration entry for enhanced versioning and platform support.

• Improvements

  • Modified test script to use a custom build script for better test management.

These changes improve platform compatibility and streamline the testing process.

[linear]

MET-522 (gate) do not recompile xtask in between tests runs

[coderabbitai]

Walkthrough

The recent updates encompass platform migration, configuration adjustments, and script modifications. The platform for the lock file has transitioned from aarch64-darwin to x86_64-linux, accompanied by a new configuration entry. Additionally, a new asynchronous function buildXtask() was introduced in the test script, and the test command in deno.jsonc was updated to use a custom script.

Changes

File Path	Change Summary
.ghjk/lock.json	Updated platform from aarch64-darwin to x86_64-linux and added a new entry with version v2.4.0.
dev/test.ts	Introduced an asynchronous function buildXtask() to build a task using Deno.
typegate/deno.jsonc	Modified test script to use ./target/debug/xtask instead of cargo x deno test.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

[Yohe-Am]

Do the same for meta-cli as well? Each test file "builds" it once with the current scheme.

[Yohe-Am]

Also, eliminate the deno task test call and go to cargo x deno test directly.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.58%. Comparing base (1f2f7ce) to head (2439b26).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #720      +/-   ##
==========================================
- Coverage   73.60%   73.58%   -0.03%     
==========================================
  Files         121      121              
  Lines       14187    14174      -13     
  Branches     1416     1415       -1     
==========================================
- Hits        10443    10430      -13     
  Misses       3717     3717              
  Partials       27       27              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[zifeo]

Nice improvement! @Yohe-Am's suggestion is great also, wanna tackle here or next?

[Natoandro]

Nice improvement! @Yohe-Am's suggestion is great also, wanna tackle here or next?

Nice improvement! @Yohe-Am's suggestion is great also, wanna tackle here or next?

I'll add it here...

The base branch was changed.