Please help understanding regression results
What does a blank space (as opposed to "pass"/"fail"/"n/a") mean in the regression table? Thanks, Arkadiy
Arkadiy Vertleyb wrote:
What does a blank space (as opposed to "pass"/"fail"/"n/a") mean in the regression table?
It means that either a test was not run or that the testing system was unable to retrieve the results. HTH, m Send instant messages to your online friends http://au.messenger.yahoo.com
"Martin Wille" <mw8329@yahoo.com.au> wrote
Arkadiy Vertleyb wrote:
What does a blank space (as opposed to "pass"/"fail"/"n/a") mean in the regression table?
It means that either a test was not run or that the testing system was unable to retrieve the results.
Hmmm, what would be possible reasons for this? How do I start figuring out what's wrong? For example, typeof gcc tests on the darwin and OSL2 (linux) passed, while the ones on your machine are left blank... Regards, Arkadiy
Arkadiy Vertleyb wrote:
"Martin Wille" wrote [...] For example, typeof gcc tests on the darwin and OSL2 (linux) passed, while the ones on your machine are left blank...
OSL's are more recent. If you checked the tests in after my latest run started then my results can't contain anything about the new tests. Regards, m Send instant messages to your online friends http://au.messenger.yahoo.com
"Martin Wille" <mw8329@yahoo.com.au> wrote
Arkadiy Vertleyb wrote:
"Martin Wille" wrote [...] For example, typeof gcc tests on the darwin and OSL2 (linux) passed, while the ones on your machine are left blank...
OSL's are more recent. If you checked the tests in after my latest run started then my results can't contain anything about the new tests.
Oh, I haven't realised how big a difference in time between tests can be... It makes sense now. Thanks, Arkadiy
Arkadiy Vertleyb wrote:
Oh, I haven't realised how big a difference in time between tests can be... It makes sense now.
Yes, the situation regarding my test runs is pretty bad currently: I can't leave the testing machine unattended currently: the old PSU broke, I added a new one, there was a expliosion inside the box (a capacitor, likely), visual inspection didn't reveal anything. I currently have to sit right next to the box in order to be able to extinguish any fires that might break out in case there's another explosion. A clean test run takes a day of CPU time. Nearly-clean runs get triggered by small changes to any one of many core libraries (MPL, type_traits, etc). Tests runs need even more attention because some of the tests don't link for intel-9.0. This results in a busy loop and I have to kill the process manually. Once I can trust the test machine again and the linking problem got fixed, results should be available more frequently again. Regards, m Send instant messages to your online friends http://au.messenger.yahoo.com
participants (2)
-
Arkadiy Vertleyb -
Martin Wille