Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.3.1SDK
-
None
Description
The CpmInitTest has faulty logic - it starts a cpm processing a bunch of docs, and then issues an async stop after 500 milliseconds. If the pipeline has already finished (say, on a fast CPU), then the tested for callback of "aborted" (which normally happens when the pipeline is stopped before it's finished) is replaced by a callback of "finished". The test case only checks for aborted.
Try fixing this to have an infinite-sized number of docs, so it doesn't "finish" before stopping.