Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,9 @@
# FLUX Conformance Test Suite

[![Tests Passing](https://img.shields.io/badge/tests-113%2F113%20v2-62%2F62%20v3-brightgreen)]()
[![Cross-Runtime Pass](https://img.shields.io/badge/cross--runtime-108%2F113%20(95.6%25)-blue)]()
[![Opcodes](https://img.shields.io/badge/opcodes-41%20implemented%20of%20247-yellow)]()
[![Languages](https://img.shields.io/badge/runtimes-Python%20%7C%20Rust%20%7C%20C%20%7C%20Go%20%7C%20WASM-purple)]()
[![ISA v3](https://img.shields.io/badge/ISA-v3%20ready-orange)]()
[![Version](https://img.shields.io/badge/version-2.0.0-blue)]()
[![License](https://img.shields.io/badge/license-MIT-green)]()
[![Paper](https://img.shields.io/badge/paper-PAPER.md-informational)]()
[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
A comprehensive conformance test suite for the FLUX bytecode virtual machine.
Verifies that all FLUX runtimes (Python, C, Go, Zig, Rust, JS, Java, CUDA)
produce identical results for the same bytecode programs.
Comment on lines +3 to +6
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Missing blank line after badge causes description to render inline with badge

Line 3 has the license badge and line 4 immediately starts the description text with no blank line in between. In Markdown, consecutive lines without a blank separator are rendered as a single paragraph. This causes "A comprehensive conformance test suite for the FLUX bytecode virtual machine. Verifies that all FLUX runtimes..." to render on the same line as the badge image, which is almost certainly not the intended layout.

Suggested change
[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
A comprehensive conformance test suite for the FLUX bytecode virtual machine.
Verifies that all FLUX runtimes (Python, C, Go, Zig, Rust, JS, Java, CUDA)
produce identical results for the same bytecode programs.
[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
A comprehensive conformance test suite for the FLUX bytecode virtual machine.
Verifies that all FLUX runtimes (Python, C, Go, Zig, Rust, JS, Java, CUDA)
produce identical results for the same bytecode programs.
Open in Devin Review (Beta)

Was this helpful? React with 👍 or 👎 to provide feedback.

Debug

Playground

Comment on lines +4 to +6
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Duplicate description paragraph introduced by PR

The PR adds a new description on lines 4–6 ("A comprehensive conformance test suite for the FLUX bytecode virtual machine. Verifies that all FLUX runtimes...") but the pre-existing line 10 already says nearly the same thing ("A comprehensive conformance test suite for the FLUX bytecode virtual machine. Verifies that all FLUX runtimes produce identical, deterministic results..."). The new text should either replace the old description or be removed to avoid redundancy.

Prompt for agents
The PR introduces a description paragraph on lines 4-6 of README.md that is nearly identical to the pre-existing description on line 10. Both say 'A comprehensive conformance test suite for the FLUX bytecode virtual machine...' Either remove the newly added lines 4-6 (keeping only the badge on line 3) or remove the old description on line 10, but having both is redundant.
Open in Devin Review (Beta)

Was this helpful? React with 👍 or 👎 to provide feedback.

Debug

Playground


> **108 of 113 cross-runtime tests pass** for a formally specified, Turing-complete bytecode ISA across Python, Rust, C, Go, and TypeScript/WASM — with all 5 failures traced to a single specification ambiguity in the confidence subsystem. Seven of ten functional categories achieve a perfect 100% pass rate.

Expand Down
Loading