Rain
Thanks! FYI this is on my queue to look at this weekend -- have a lot of stuff at work this week. I like the pretimeout state :) It's currently...
Still in the queue to review -- higher priority stuff came up but I'm hoping to carve out some time this weekend.
I know things have been a bit behind here, but wanted to let you know that I ended up using a lot of this implementation for the new [wrapper script](https://nexte.st/docs/configuration/wrapper-scripts/)...
Yeah wrapper scripts can definitely fulfill this role! But ease of use is an important consideration: * Nextest manages timeouts but has no clear way of communicating that to the...
Let's leave this open, I'll try and finish it up some time soon if you don't get to it. I feel like around 50% of this landed already.
Thanks for picking this up. Let me rebase on to main and then you can submit your work as dependent on it. > But how can nextest detect when it's...
Rebased this on main.
Thanks! I think the general suggestion makes sense, and I like the `stdout=never,stderr=immediate` approach. In the specific case of the output generated by libtest, I actually want to just start...
> For combined outputs I would expect that it would apply the filter before combining them. Ah sadly that's not possible on Unix.
> Then I would suggest only supporting never when using libtest output, and returning an error when a user inputs stdout=never or stderr=never or a combination of the two. I...