Ah, and it seems like simulation mode stops and prints a trace if it finds a violation, with a nonzero exit code. Perfect, thanks!
Hi Jesse,
TLC won't serialize the generated traces if you run it without (the optional) `file=output_dir`. The purpose of the `file` sub-command is to serialize traces if one wants to post-process them with third-party tools or subsequent TLC runs.
Markus
> On Jul 4, 2024, at 7:30 PM, A. Jesse Jiryu Davis <jesse@xxxxxxxxxxxxxxx> wrote:
>
> Thanks for the quick answer as usual Markus, this is helpful. I'll try simulation mode.
>
> Is there a way to prevent TLC from outputting a trace file for successful runs (runs without invariant violations)? I want to run a lot of simulations to ease my anxiety about deeply-hidden bugs, e.g.:
>
> java -jar tla2tools.jar -simulate num=100000,file=output_dir/ mcMySpec.tla -workers 8 -cleanup -deadlock
>
> This produces num * workers = 800000 traces, and the output_dir/ directory grows very large. On macOS it takes a lot of disk space and it takes a very long time to delete! I want to output a trace only if/when there's an invariant violation.
--
You received this message because you are subscribed to the Google Groups "tlaplus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tlaplus+unsubscribe@xxxxxxxxxxxxxxxx.
To view this discussion on the web visit https://groups.google.com/d/msgid/tlaplus/C1529442-1659-4E86-AB1C-2B30239A737A%40lemmster.de.