I'm not sure what changed - it was certainly not a ducktape code change, nor it was a vagrant ubuntu base box change (because I've tested with older boxes explicitly, unless vagrant can update some parts of older boxes without bumping their version). It could be that something silently updated vagrant itself? Or a MacOS change? Unlikely though.
Anyways, right now if I run ducktape system tests on my local machine, then the test_kill_process would fail saying operation not permitted. Turns out when the test is doing grep -i nc, the first line in the output is /usr/sbin/irqbalance --foreground, which cannot be killed (well, maybe with sudo? not through normal means). So I'm updating the test to be more precise about what it greps for, even if I don't understand where the irqbalance is even coming from.
I'm not sure what changed - it was certainly not a ducktape code change, nor it was a vagrant ubuntu base box change (because I've tested with older boxes explicitly, unless vagrant can update some parts of older boxes without bumping their version). It could be that something silently updated vagrant itself? Or a MacOS change? Unlikely though. Anyways, right now if I run ducktape system tests on my local machine, then the
test_kill_processwould fail sayingoperation not permitted. Turns out when the test is doinggrep -i nc, the first line in the output is/usr/sbin/irqbalance --foreground, which cannot be killed (well, maybe with sudo? not through normal means). So I'm updating the test to be more precise about what itgreps for, even if I don't understand where theirqbalanceis even coming from.