Skip to content

feat(ci): WASI component smoke tests — hello_rust, calculator, datetime#199

Open
avrabe wants to merge 1 commit intomainfrom
feat/ci-component-smoke-tests
Open

feat(ci): WASI component smoke tests — hello_rust, calculator, datetime#199
avrabe wants to merge 1 commit intomainfrom
feat/ci-component-smoke-tests

Conversation

@avrabe
Copy link
Copy Markdown
Collaborator

@avrabe avrabe commented Apr 3, 2026

Summary

Adds runtime smoke tests to CI that actually execute WASI components through kilnd:

  • hello_rust.wasm → verifies "Hello wasm component world from Rust!"
  • calculator.wasm 8 + 8 → verifies "8 + 8 = 16"
  • datetime.wasm → verifies "Hello Rust on ..."

Downloads pre-built components from pulseengine/wasm-component-examples v0.2.0. Runs in the core_tests_and_analysis job on every PR and push.

This catches regressions in the full pipeline: decoder → validator → runtime → WASI → component model.

Test plan

  • All 3 components verified locally
  • VxWorks cross-compilation passing on main

🤖 Generated with Claude Code

Downloads pre-built WASI component examples from
pulseengine/wasm-component-examples v0.2.0 and runs them through
kilnd, verifying expected output:

- hello_rust.wasm → "Hello wasm component world from Rust!"
- calculator.wasm 8 + 8 → "8 + 8 = 16"
- datetime.wasm → "Hello Rust on ..."

Runs in the core_tests_and_analysis job on every PR and push.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 3, 2026

🔍 Build Diagnostics Report

Summary

Metric Base Branch This PR Change
Errors 0 0 0
Warnings 5 5 0

🎯 Impact Analysis

Issues in Files You Modified

  • 0 new errors introduced by your changes
  • 0 new warnings introduced by your changes
  • 0 total errors in modified files
  • 0 total warnings in modified files
  • 0 files you modified

Cascading Issues (Your Changes Breaking Other Files)

  • 0 new errors in unchanged files
  • 0 new warnings in unchanged files
  • 0 unchanged files now affected

Note: "Cascading issues" are errors in files you didn't modify, caused by your changes (e.g., breaking API changes, dependency issues).

✅ No Issues Detected

Perfect! Your changes don't introduce any new errors or warnings, and don't break any existing code.


📊 Full diagnostic data available in workflow artifacts

🔧 To reproduce locally:

# Install cargo-kiln
cargo install --path cargo-kiln

# Analyze your changes
cargo-kiln build --output json --filter-severity error
cargo-kiln check --output json --filter-severity warning

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant