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
Previously, if a workload is run with a long duration, some of the consistency
checks would be skipped. This check is only done when running a workload, but
some tests also run a separate post check.
This post check is not aware of the previous workload's duration and will run
the checks even if the workload is run with a long duration.
This change adds a new flag, `last-duration`, which can be used to set the
duration of the previous workload run. This flag can be used during a post
consistency check to determine which checks to skip for long duration workloads.
Epic: None
Release note: None
"This is an optional parameter to specify AOST; used exclusively in conjunction with the TPC-C consistency "+
322
354
"check. Example values are (\"'-1m'\", \"'-1h'\")")
323
355
g.flags.BoolVar(&g.literalImplementation, "literal-implementation", false, "If true, use a literal implementation of the TPC-C kit instead of an optimized version")
356
+
g.flags.Var(&lastDurationSetter{val: &[]time.Duration{0}[0], tpcc: g}, "last-duration", "The duration of the previous workload run (Used to determine which consistency checks to skip for long duration workloads).")
0 commit comments