Satheesh Rajendran

> > > I like the idea, but can you rename this to something like "monitoring jobs" or similar? It's not really clear what "profiler" is supposed to mean in...

test pending...

result: $ ./op-test -c ltcalpine-lp8.conf --run testcases.RunHostTest.RunHostTest --enable-monitors ``` ... ... [console-expect]#which whoami && whoami /usr/bin/whoami root [console-expect]#echo $? echo $? 0 [console-expect]#stress-ng --cpu 80 --timeout 20s stress-ng --cpu 80...

@oohal Have addressed all comments, pls merge if no further comments, Tnx!

rebased...

@oohal pls help merge if no further comments, tnx!

Looks like there is a external runner, http://tungwaiyip.info/software/HTMLTestRunner.html http://tungwaiyip.info/software/HTMLTestRunner_0_8_2/HTMLTestRunner.py, we might need similar one implemented inside op-test framework.

yes, that will do, we can add those packages to requirements.txt for user aware. how about having `--html{,xml,...}-report` in command line option through which we can demand framework to generate...

> Therefore, the path to address those two issues could be create separate daemon and config class by simulating currently existed good examples. @chunfuwen yep, good approach, have any one...

this will be a bottle neck for future test executions, and one more thing to consider is to retain the backward compatibility... for older distributions...