Integration test of builders

[tuler]

integration tests for builders

[changeset-bot]

⚠️ No Changeset found

Latest commit: b553b59

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Coverage Report for ./apps/cli

Status	Category	Percentage	Covered / Total
🔵	Lines	28.52%	247 / 866
🔵	Statements	28.6%	250 / 874
🔵	Functions	32.03%	41 / 128
🔵	Branches	23.63%	95 / 402

File Coverage

File	Stmts	% Branch	% Funcs	% Lines	Uncovered Lines
Changed Files
apps/cli/src/exec.ts	75%	64.28%	100%	75%	42, 45, 88-92, 96-97, 100
apps/cli/src/builder/directory.ts	100%	100%	100%	100%

Generated in workflow #164 for commit b553b59 by the Vitest Coverage Report Action

[endersonmaia]

Requested some changes in the test case descriptions, didn't do for every case, but hope you get the idea.

[endersonmaia]

I'm approving, but will suggest some improvements for other PRs.

The fallback message should be a WARN message with less details.

Instead of error executing 'xgenext2fs', falling back to docker execution using image 'cartesi/sdk:0.11.0' we cold shw something like:

WARN: xgenext2fs not found, using cartesi/sdk container image

For better builder code coverage, we should also include tests for sqfs type filesystems.

[tuler]

For better builder code coverage, we should also include tests for sqfs type filesystems.

done

[tuler]

Instead of error executing 'xgenext2fs', falling back to docker execution using image 'cartesi/sdk:0.11.0' we cold shw something like:

yeah, interpreting the errors raised by xgenext2fs cli is kind of hard