Running PASS Record — Java, JVM, Native C/C++, and SLeeLa VM
Record ID: RUNNING.PASS.JAVA.001 Edition: 1.0 Recorded: 2026-11-07 (UTC, GitHub Actions timestamps) Repository: mearvk/SLeeLa · Branch: master · SLeeLa baseline: Syntax 3.0 Status: PASS — corrected cross-platform baseline
1. Executive result
The corrected Comparison Standards Conformance workflow completed successfully on Ubuntu, macOS, and Windows. The SLeeLa Syntax 3.0 compiler/VM vector job also completed successfully on Ubuntu.
The strongest single confirmation is run 42331591283, whose four jobs all concluded successfully:
- Ubuntu native C/C++/Java shared vectors.
- macOS native C/C++/Java shared vectors.
- Windows native C/C++/Java shared vectors.
- SLeeLa Syntax 3.0 compiler/VM build and shared-vector execution on Ubuntu.
This certifies the tested baseline only. It does not claim complete language conformance, complete ABI qualification, or performance superiority.
2. Verified run ledger
| Run ID | Overall result | UTC start | Evidence |
|---|---|---|---|
| 42331591283 | PASS | 2026-11-07 02:55:48 | Four of four jobs passed |
| 42331589662 | PASS | 2026-11-07 02:55:47 | Four of four jobs passed |
| 42331561514 | PASS | 2026-11-07 02:55:24 | Four of four jobs passed |
| 42331558757 | FAIL | 2026-11-07 02:55:22 | Corrective iteration; retained as historical failure |
| 42331126707 | FAIL | 2026-11-07 02:49:43 | Initial run exposed Windows Java-launch and VM-output comparison issues |
The three successful runs are separate workflow executions of the same current baseline, not three distinct feature suites.
3. Latest run: job-by-job evidence
Run: 42331591283 Conclusion: success Commit: 83e87b1344e7c941821132127568510e24396b21
| Job | Platform / environment | Result |
|---|---|---|
| Shared vectors | Ubuntu latest | PASS |
| Shared vectors | macOS latest | PASS |
| Shared vectors | Windows latest | PASS |
| SLeeLa Syntax 3.0 VM vectors | Ubuntu latest | PASS |
The Ubuntu job completed the POSIX shared C, C++, and Java step. macOS completed Java 21 setup and the POSIX shared-vector step. Windows completed MSYS2 UCRT64 toolchain setup, Java 21 setup, native Windows Python setup, compiler PATH setup, and the Windows shared-vector step. SLeeLa completed prerequisite installation, ephemeral manifest generation, compiler/VM build, shared vector execution, and output artifact retention. All steps in the four jobs concluded successfully.
4. Visual result summary
Latest completed run
Ubuntu shared vectors PASS ██████████ 1/1 macOS shared vectors PASS ██████████ 1/1 Windows shared vectors PASS ██████████ 1/1 SLeeLa VM vectors (Ubuntu) PASS ██████████ 1/1 4 / 4 jobs
Three corrected runs
42331561514 PASS ██████████ 4/4 jobs 42331589662 PASS ██████████ 4/4 jobs 42331591283 PASS ██████████ 4/4 jobs 12 / 12 job conclusions successful
These bars visualize GitHub job conclusions only. They are not execution-speed, benchmark, reliability-rate, or statistical-performance measurements.
5. Shared test-vector scope
| Test dimension | Baseline behavior | Current evidence |
|---|---|---|
| Integer arithmetic | Addition / multiplication producing 42 | PASS in shared vector jobs |
| Bounded iteration | Accumulation producing 15 | PASS in shared vector jobs |
| Text output | ASCII output hello | PASS in shared vector jobs |
| SLeeLa compiler/VM | Build and execute Syntax 3.0 vector | PASS on Ubuntu |
| Cross-platform native/Java parity | C11, C++17, Java 21 | PASS on Ubuntu, macOS, Windows |
The SLeeLa VM output validator checks the final three nonblank program-output lines. Runtime verification or memory-manager diagnostics may precede those lines; the validator does not mistake that preamble for application output.
6. Corrective engineering record
The first completed run, 42331126707, exposed two independent integration issues.
6.1 Windows Java tool discovery
Observed: C11 and C++17 succeeded, but Java compilation failed because Python running in the MSYS2 environment could not resolve the Windows javac executable (WinError 2).
Correction: The workflow now runs the test harness with native Windows Python, configures Java 21 using actions/setup-java, and adds the MSYS2 UCRT64 compiler directory to the Windows PATH.
Verification: The Windows shared-vector job passed in run 42331591283.
6.2 SLeeLa runtime diagnostics and vector comparison
Observed: The SLeeLa compiler/VM built and executed the test program, but runtime/security and memory-manager diagnostics appeared in stdout. Strict comparison of the entire output therefore failed even though the expected program-output lines were present.
Correction: comparison/tests/check_sleela_output.py validates the final three nonblank output lines against 42, 15, and hello, while allowing a diagnostic preamble.
Verification: The SLeeLa VM build, execution, validator, and output-retention steps all passed in run 42331591283.
7. Retained CI artifacts
Run 42331591283 retained the following artifacts, which were not expired when this report was prepared:
| Artifact | Purpose |
|---|---|
| comparison-vectors-ubuntu-latest | Native/Java result record for Ubuntu |
| comparison-vectors-macos-latest | Native/Java result record for macOS |
| comparison-vectors-windows-latest | Native/Java result record for Windows |
| comparison-vectors-sleela-vm | SLeeLa VM program output |
Open the workflow run to inspect and download these artifacts. GitHub retention policy may cause artifacts to expire.
8. What this PASS does — and does not — establish
Established by this run:
- Shared C11, C++17, and Java 21 test harness completed successfully on all three configured operating systems.
- Windows-specific compiler and Java tool setup completed successfully.
- SLeeLa Syntax 3.0 compiler/VM built and executed the shared vector on Ubuntu.
- Expected common output was accepted by the SLeeLa output validator.
- All four jobs in the latest workflow run completed successfully.
Not established yet:
- Complete SLeeLa language conformance or complete Java/JVM conformance.
- Numeric overflow, floating-point edge behavior, Unicode semantics, locale behavior, or complete string semantics.
- Memory safety, garbage-collection correctness, ownership/lifetime equivalence, or sanitizer qualification.
- Stable C ABI compatibility across compilers/platforms, or C++ ABI compatibility.
- Java process delegation, JNI, or embedded-JVM lifecycle behavior.
- Concurrency, atomics, memory ordering, thread safety, or deterministic scheduling.
- Performance, throughput, latency, memory footprint, or energy use.
- SLeeLa VM qualification on Windows or macOS.
No performance graph or speed ranking is included because this workflow is a correctness smoke test, not a benchmark.
9. Recommended next qualification stages
- SCS-3 expansion: add edge cases for integer widths, signedness, overflow policy, floating-point behavior, strings, Unicode, arrays, and bounds.
- Memory qualification: add ownership/lifetime tests, leak checks, and supported sanitizers for native C/C++.
- ABI qualification: compile C ABI consumers with multiple toolchains; test C++ wrappers without allowing exceptions to cross the C boundary.
- Java integration: test process arguments, environment, standard streams, exit codes, timeouts, and error propagation. Treat JNI and embedded JVM as separate optional profiles.
- VM platform coverage: add SLeeLa VM build/execution jobs on Windows and macOS when supported toolchains and runtime dependencies are ready.
- Performance suite: establish warm-up policy, repetitions, workload definitions, hardware/runner metadata, and statistical summaries before publishing speed comparisons.
Each stage must add executable tests, identify exact toolchain/platform versions, and retain its own result artifact before its matrix status changes to PASS.
10. Reproduction and authoritative links
- Comparison Standards workflow
- Comparison directory README
- Conformance matrix
- Shared test vectors
- Latest successful workflow run
- Previous successful run
- Previous successful run
- Initial failing run and diagnostic evidence
Reproduction: push or open a pull request touching comparison/, impl/, or the workflow; alternatively, use GitHub Actions workflow_dispatch on the Comparison Standards Conformance workflow.
Record conclusion: The corrected cross-platform Java/JVM/native baseline and the SLeeLa Syntax 3.0 VM baseline are passing in GitHub Actions. This record certifies only the tests and environments explicitly listed above.