You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running jreduce with --dump on some benchmarks, it throws an error.
The error disappears when the --dump option is removed, but the tool runs too many iterations (450 iterations, ~45minutes, after which the run was manually terminated)
It might be a bug in the reverse lookup of the variable names. I will look at it eventually, but for now a work around as you mention it yourself is to not enable the --dump flag.
The error disappears when the --dump option is removed, but the tool runs too many iterations (450 iterations, ~45minutes, after which the run was manually terminated)
Why is 450, too many iterations? 450 might be a reasonable number of iterations depending on the predicate.
Right. I don't know why I thought 450 was too many iterations.
But I tried running again, and it did not terminate in 5 hours (even though a timeout of 1800 was set) on 2 of the benchmarks I tried. Should I create a separate bug report for that?
When running jreduce with --dump on some benchmarks, it throws an error.
The error disappears when the --dump option is removed, but the tool runs too many iterations (450 iterations, ~45minutes, after which the run was manually terminated)
Here is the workfolder
https://drive.google.com/file/d/1aL8GT9vOgRwFWR3ISCa1llCu_Bpudfcf/view?usp=sharing
Here is the error-log.
10:51:21 ├ JReduce
10:51:21 │ ├ Started JReduce.
10:51:21 │ ├ Reading inputs
10:51:21 │ │ └ 0.000s
10:51:21 │ ├ Calculating Initial Problem
10:51:21 │ │ ├ setup
10:51:21 │ │ │ └ 0.054s
10:51:21 │ │ ├ run
10:51:22 │ │ │ └ 1.276s
10:51:22 │ │ └ 1.332s
10:51:22 │ ├ Refining Problem
10:51:22 │ │ └ 0.015s
10:51:22 │ ├ Initializing key function
10:51:22 │ │ ├ Calculating the hierarchy
10:51:22 │ │ │ ├ Load stdlib stubs
10:51:29 │ │ │ │ └ 6.500s
10:51:29 │ │ │ ├ Load project stubs
10:51:31 │ │ │ │ └ 1.681s
10:51:31 │ │ │ ├ Compute hierarchy
10:51:33 │ │ │ │ └ 1.995s
10:51:33 │ │ │ ├ Dumping stubs
10:51:37 │ │ │ │ └ 4.542s
10:51:37 │ │ │ └ 14.720s
10:51:37 │ │ ├ Found 3404 items.
10:51:37 │ │ ├ Found 3402 facts.
10:51:37 │ │ ├ The core is 96 of them.
10:51:37 │ │ └ 14.770s
10:51:37 │ ├ Compute CNF
10:51:43 │ │ └ 6.089s
jreduce: Maybe.fromJust: Nothing
CallStack (from HasCallStack):
error, called at libraries/base/Data/Maybe.hs:148:21 in baseata.Maybe
fromJust, called at src/JReduce/Logic.hs:519:40 in jreduce-0.1.0-Abs4ufFiDadAKpDliDdD1j:JReduce.Logic
CallStack (from -prof):
JReduce.Logic.describeLogicProblem..showGraphVar (src/JReduce/Logic.hs518,5)-(519,67))
JReduce.Logic.describeLogicProblem.\ (src/JReduce/Logic.hs481,91)-(556,5))
JReduce.Logic.describeLogicProblem (src/JReduce/Logic.hs481,1)-(556,5))
JReduce.Logic.CAF:lvl35_r1uUy ()
The text was updated successfully, but these errors were encountered: