Bug #102

iocoChecker takes too long, and also preparing results for showing may take long time

Added by Axel Belinfante over 11 years ago. Updated over 10 years ago.

Status:ClosedStart date:11 Jun 2009
Priority:NormalDue date:
Assignee:-% Done:


Target version:1.3.0


after iocochecker seems to have finished, it may take quite some time before results are presented
(at least when fwgc model s4 is checked against itself)

Related issues

Related to JTorX - Bug #270: uncaught out-of-memory error in IocoCheckerWrapper.getFai... Closed 13 Jan 2010
Related to JTorX - Bug #96: on windows, the iocoChecker run out of memory when testin... Resolved 11 Jun 2009


#2 Updated by Axel Belinfante over 10 years ago

  • Target version set to 1.3.0
  • % Done changed from 80 to 100

#3 Updated by Axel Belinfante over 10 years ago

  • Status changed from New to Closed

Also available in: Atom PDF