[Soundness] Daily Soundness Validation - January 28, 2026 #8415
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-02-04T11:57:11.792Z. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
🎉 Status: Zero Open Issues with "Soundness" Label
This is excellent news! The Z3 repository currently has 0 open issues labeled with "soundness", indicating that the solver's correctness is in a strong state.
Currently Monitored Issues
While no issues carry the "soundness" label, three open issues with potential soundness implications are being tracked:
🔴 Critical Issues
Issue #8397 - Soundness issue in Real (seemingly unrelated to Float)
@levnachsat, CVC5 reportsunsat(solver disagreement)Issue #8345 - Soundness issue by converting from bit representation to fp to Real
falseusing incremental solvingIssue #8292 - ASSERTION VIOLATION File: ../src/util/mpzzp.h Line: 139
@NikolajBjorner,@levnach,@Copilotto_int/to_realconversionsWorkflow Status: Build Environment Issue
This automated validation workflow cannot compile Z3 due to missing build tools in the GitHub Actions runner environment. This has been a blocker across all 22 workflow runs since inception.
Missing:
ar,gcc,g++,cmake,makeImpact:
Required Fix
The workflow YAML needs this addition:
What This Workflow Provides Today
Despite the build limitation, the workflow continues to provide value:
Recommendations
For Workflow Maintainers
For Z3 Maintainers
@NikolajBjorner- may be in progressStatistics
Next Scheduled Run
Daily at 11:47 UTC
Expected Outcome: Continued monitoring; validation remains blocked without build environment fix.
This is an automated report from the Soundness Bug Detector workflow. Test cases and detailed tracking data are preserved in workflow cache memory.
Beta Was this translation helpful? Give feedback.
All reactions