search for: qrt

...to -upsdev, since it has not to be private... please note that revisions 3771 and 3772 conclude nut_clock_* > development (including UTs): > interestingly enough, we were talking about that 5 mn ago with Emilien ;) my conclusion was that nut_clock devs were completed with 3772, and only the QRT side was remaining. but that last requires: 1) that I provide you with a procedure to setup QRT (and this requires me to push a fix upstream to Ubuntu) 2) that we have a jail mechanism to execute QRT, including system clock changes to not impact negatively the buildbot system. thus, postponed for...

...through the existence of POWERDOWNFLAG and the execution of SHUTDOWNCMD I have still a good TODO list on this. All these information, including how to run the script, are located in the script header. I've attached this script, for reference, and it's also available as a patch for Ubuntu QRT (QA Regression Testing): https://bugs.launchpad.net/qa-regression-testing/+bug/894476 Part of the future improvements, I'm willing to tie this script to the NUT test plan and test cases, at least the part that can be automated, and to integrate it part of the 'check' target. Once done,...

?Hello Arnaud, Charles, regarding the nut_clock_* iface unit testing, I came to the following conclusion: 1/ It is IMO generally impossible to do deterministic unit test; the problem in question is inherently non-deterministic (I mean non-det. by nature). Justification: the main reason is that we can't perfectly predict the CPU time spent on computation, mainly because we have multi-tasking;