fix(lua): port eval/computed-key dynamic-call detection to WASM extractor · optave/ops-codegraph-tool@2810b4c

Triggered via pull request July 8, 2026 14:56

carlos-alm

opened #2043

fix/issue-1909-lua-wasm-extractor-missing-eval-computed-key

Status Failure

Total duration 11m 15s

Artifacts 1

perf-canary.yml

on: pull_request

Perf canary (incremental tiers)

11m 11s

Annotations

3 errors and 5 warnings

Perf canary (incremental tiers)

Process completed with exit code 1.

tests/benchmarks/regression-guard.test.ts > Benchmark regression guard > incremental benchmarks > wasm engine — dev vs 3.15.0: tests/benchmarks/regression-guard.test.ts#L521

AssertionError: Benchmark regressions exceed threshold: 1-file rebuild: 113 → 317 (+181%, threshold 150%) ❯ assertNoRegressions tests/benchmarks/regression-guard.test.ts:521:12 ❯ tests/benchmarks/regression-guard.test.ts:739:9

tests/benchmarks/regression-guard.test.ts > Benchmark regression guard > incremental benchmarks > native engine — dev vs 3.15.0: tests/benchmarks/regression-guard.test.ts#L521

AssertionError: Benchmark regressions exceed threshold: 1-file rebuild: 117 → 293 (+150%, threshold 100%) ❯ assertNoRegressions tests/benchmarks/regression-guard.test.ts:521:12 ❯ tests/benchmarks/regression-guard.test.ts:739:9

Benchmark Regression

[wasm] 1-file rebuild: 113 → 317 (+181%, threshold 15%)

Benchmark Regression

[wasm] No-op rebuild: 23 → 28 (+22%, threshold 15%)

Benchmark Regression

[wasm] Full build: 12219 → 15525 (+27%, threshold 15%)

Benchmark Regression

[native] 1-file rebuild: 117 → 293 (+150%, threshold 15%)

Benchmark Regression

[native] Full build: 3521 → 4986 (+42%, threshold 15%)