Rain
> Sounds pretty neat, is there a way nextest could leverage the same infrastructure? Hmm, so a thing I realized is that nextest currently always passes in `--nocapture`, whether it...
While writing this, I sadly realized that --nocapture is pretty load bearing for tests that time out -- we want to show whatever output the test produced by the time...
What if a test sets a SIGUSR1 handler for itself? I don't know how common that is but it is a thing that's possible. To be honest I still don't...
Thanks! I hadn't thought about using the concurrency setting. I think unfortunately in my use it would still be subject to races depending on which job goes first; it would...
BTW, this use case: > to allow jobs to trigger behavior based on nothing being released (or something being released), including reporting in PRs if it will cause a release...
Any thoughts about this? This is blocking moving to a newer cargo-release (my jobs are currently pinned to 0.21.4). If we agree on a way forward I'm happy to implement...
I just ran into another race: if cargo-release attempts to publish the same version of a crate in two separate jobs, the one that loses the race will fail, even...
OK, I'm going to go ahead and implement my preferred design in a personal fork. I'd be happy to work on upstreaming it whenever you have the time :)
Thanks Tony! Do you think you could work with Cargo upstream to clarify the situation?
Maybe we could provide general advice and a list of special cases to consider.