Actually I see this occasionally here now as well (but not always).
Could this be related to the recent when error handling changes in
f7440375?
Robin
It's definitely related to that change because it's the associated test I made to try to specifically exercise the Trigger code. I've seen it a couple times, too. It's probably just a reliability issue with the test that I need to figure out -- I think Bro decides it's done when no more packets are available, but there's still pending Triggers that the test needs to have execute for it to pass.
Jon