-
Notifications
You must be signed in to change notification settings - Fork 0
T-009: Add GitHub Actions build badges #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,13 +1,9 @@ | ||
| # FLUX Conformance Test Suite | ||
|
|
||
| []() | ||
| [-blue)]() | ||
| []() | ||
| []() | ||
| []() | ||
| []() | ||
| []() | ||
| []() | ||
| [](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
+4
to
+6
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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 agentsWas this helpful? React with 👍 or 👎 to provide feedback. Debug |
||
|
|
||
| > **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. | ||
|
|
||
|
|
||
There was a problem hiding this comment.
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.
Was this helpful? React with 👍 or 👎 to provide feedback.
Debug
Playground