Invalid data is shown if an error happened during testing

[andrasfuchs]

When I test Db4objects, Perst, VelocityDB and Volante with 100'000 records:

• Db4o completes successfully, but the end of the read charts are missing
• Perst completes successfully
• VelocityDB write ends at around 80'000, read and secondary at 50'000 records
• Volante write is ok, read stops at 35'000, secondary read doesn't even start

Values are displayed for all though in the end results. At least we should display an error message to warn the user that the displayed values are most likely incorrect or at least incomplete.

[krisdimitrov]

When you test databases with less records (50 000 - 500 000) some of the databases are so fast that the chart cannot draw them when the timers tick. This can be fixed with a very fast timer, but its not nessesary because tests with that much records are meaningless by themselves.

I will consider your proposition for the error message though. I've been thinking for a while how to implement it so that it looks nice for the users.