Feature #760
Make AutoTest more portable + Watchdog support
| Status: | Approved | Start date: | 04/24/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Miroslav Fidler | % Done: | 0% | |
| Category: | General | Spent time: | - | |
| Target version: | - |
Description
Attached patch makes AutoTest bit more configurable, allowing to run it easily on different systems. The defaults were kept to mimic previous behavior. Nice side effect of the changes is that I can run two instances of AutoTest in parallel now, thanks to the new options.
Also, option to produce Watchdog-parseable output was added.
One more thing to think about would be if we really need to so careful. Doing millions of string, heap etc. operations is nice, but perhaps we could lower it a bit and use the computing power to test it on more platforms... Chance to hit a problem would stay the same for serious bugs (at least those that affect all platforms). Or we could at least split the short test and long test in separate test-suites, so the short tests could be run for each revision of U++ and the longer ones less often.
AutoTest.patch 
(2.05 KB)
History
#1 Updated by Miroslav Fidler about 10 years ago
- Status changed from Patch ready to Approved
After fixing small bug, applied.
One more thing to think about would be if we really need to so careful. Doing millions of string, heap etc. operations is nice, but perhaps we could lower it a bit and > use the computing power to test it on more platforms... Chance to hit a problem would stay the same for serious bugs (at least those that affect all platforms). Or we
could at least split the short test and long test in separate test-suites, so the short tests could be run for each revision of U++ and the longer ones less often.
Actually, I am a little bit nervous about reducing the time of these "carpet bombing" tests for autotest to have realistic times... I remember that in some cases, the error was produced after about hour and I used to run the test for several days.. :)
But splitting is perhaps a good idea. I will do that with other changes I plan (e.g. I would like to compile with gcc too, but perhaps not run).