Repository navigation
Report UNKNOWN when the target never reaches main - #89
Closed
nils-loose wants to merge 3 commits into
Closed
nils-loose wants to merge 3 commits into
nils-loose wants to merge 3 commits into
Conversation
The executor sends a trace whenever the entry method was entered, also when it ends in an exception or System.exit. A round without one never reached main (VerifyError, missing main class, agent failure), so it was wrongly taken for a non-symbolic program and reported SAFE. Such a round now records a no_trace execution error and ends the analysis with UNKNOWN; the divergence check is skipped for it, as the latest trace is an older one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A task without a class Main, or one that does not compile, ends in a ClassNotFoundException for Main when run through run_swat.py. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nils-loose
added a commit
that referenced
this pull request
Oct 19, 2026
SVCompDriver.py: one no_trace mechanism. run_testcase decides received_trace once (#89); a run without one is not checked for divergence and, after the output scan, ends UNKNOWN with a single no_trace error, which names the branch #72 used to record it for. A run stopped by the resource budget (#88) is handled before, as in #88. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nils-loose
added a commit
that referenced
this pull request
Oct 19, 2026
…property Combining #73 and #89: after round 0 a proof turned the verdict into SAFE, also for a run that never reached main (no trace), which #89 ends UNKNOWN. The proof now applies only when round 0 sent a trace. The no-trace tests get the Database reads, the pre-check and the budget of the other PRs; #72's robustness test no longer expects no_trace for a failed (ERROR) run, which ends UNKNOWN by itself. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #87
What changed
When the target JVM failed before
mainran (VerifyError,ClassNotFoundException: Main, a task that did not compile in the competition package, an agent crash inpremain), no trace reached the explorer. The SV-COMP driver then saw zero symbolic variables, took the run for a non-symbolic program (== NON-SYMBOLIC), and reported SAFE.The executor sends a trace whenever the entry method was entered, also when the method ends in an exception (surrounding try/catch, then
Intrinsics.terminate) or inSystem.exit(shutdown hook). The trace POST is synchronous. So a trace arriving during a round is the positive signal thatmainran.Database.trace_count()is new.run_testcasecompares the count before and after each target run.no_traceexecution error instats.jsonand ends with UNKNOWN. This check runs after the output scan, so anAssertionErrorthat the program itself throws beforemain(for example in the main class's static initializer) is still reported as VIOLATION. A[SWAT Exception]or SWAT assertion still gives UNKNOWN, as before.run_swat.pyonly relays the explorer's verdict line, so the competition package is covered by the same change.Measurement
360 runs, competition config (
--sv-comp, 300 s, mem15g, nosa), compared with the baseline:[SWAT Exception]and similar);No run in the set hit the new
no_tracepath, so no verdict changes on the benchmarks. Three cases came out different, and none of them is a real verdict change:Net: 0 points, 0 new wrong verdicts.
Reproducers, base vs. this branch:
B extends A, run with aBthat does not extendA)Main(explorer)Main/ task does not compile (run_swat.py,ClassNotFoundException: Main)Tests
symbolic-explorer/tests/test_no_trace.py: unit tests fordetermine_next_stepand for howrun_testcasederivesreceived_trace.symbolic-explorer/tests/test_failed_start_e2e.py: the reproducers above, run end to end through the explorer and through the package wrapper (run_swat.pyin the package layout). Skipped when the executor jar, the Z3 libraries or javac are missing. The failed-start cases fail on the base and pass here.Known limits
useAbortTimer, off insv-comp.cfg), an aborted run sends no trace and now gives UNKNOWN instead of SAFE.🤖 Generated with Claude Code