Current status: Fix typo in property (1 min) → rerun verification (50 min) → fix typo in property (3 min) → rerun verification (90 min) → fix typo in property (1 min) → rerun verification (45 min) → ⋯
-
-
Replying to @oe1cxw
I am always talking about importance of type safety and tooling support with real-time error highlight.. people call me mad and keep writing scripts :)
1 reply 0 retweets 0 likes -
Replying to @ITMayWorkDev
Not that kind of typos. Bitmaps with properties of physical memory regions and I kept setting the wrong bits..
1 reply 0 retweets 0 likes -
Replying to @oe1cxw
I see... have you considered running large amount of parallel subtasks in e.g. AWS lambda if verification can be split?
1 reply 0 retweets 0 likes -
Replying to @ITMayWorkDev
This is one subtask of 79. I did re-run just the one task so I don't waste too much compute resources. (It's one of the easier task in the set. The whole thing takes about a day on an AWS c4.4xlarge instance.)
1 reply 0 retweets 0 likes -
Replying to @oe1cxw
So this one task cannot be split and takes 50 mins to run?
1 reply 0 retweets 0 likes -
Replying to @ITMayWorkDev
Yes. More like 120-180 minutes if you don't accidentally add a bug that the solver can find quickly. Luckily that's what the typos did..
1 reply 0 retweets 0 likes
SAT/SMT solvers are inherently hard to parallelize. The best method so far is to run multiple solver instances on the same problem with slightly different tuning parameters and hope that one of those will finish slightly sooner than the others.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.