You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
It spins for as long as I let it run or until it bumps into ulimit, RES grows at about 16M per 10 seconds.
There's not much difference in output with git head, apart from outputting Executing lines when gathering information at startup the only differences in output are that it doesn't print "[New thread 395121]" after "NetperfDemoRunner TCP download::4 finished" and timers expire in a different order, here's the diff
NetperfDemoRunner TCP download::1 finished
NetperfDemoRunner TCP download::3 finished
NetperfDemoRunner TCP download::4 finished
-[New thread 395121]
PingRunner Ping (ms) ICMP finished
Runner aggregation finished
TimerRunner Watchdog [Ping (ms) ICMP]: timer expired
TimerRunner Watchdog [Ping (ms) ICMP] finished
TimerRunner Watchdog [TCP download::2]: timer expired
TimerRunner Watchdog [TCP download::2] finished
-TimerRunner Watchdog [TCP download::1]: timer expired
-TimerRunner Watchdog [TCP download::4]: timer expired
-TimerRunner Watchdog [TCP download::1] finished
TimerRunner Watchdog [TCP download::3]: timer expired
-TimerRunner Watchdog [TCP download::4] finished
TimerRunner Watchdog [TCP download::3] finished
+TimerRunner Watchdog [TCP download::4]: timer expired
+TimerRunner Watchdog [TCP download::4] finished
+TimerRunner Watchdog [TCP download::1]: timer expired
+TimerRunner Watchdog [TCP download::1] finished
I'll add some prints in aggregators.py to try to figure out where it's spinning and get back to you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.