@vito something extremely odd is

[outer musk]

What kind of output are we talking? Logs or spans?

[viscid storm]

Both, I think? I also went up in verbosity mode with + a few times now that I think about it (probably equiv of -vvv).

Also, it looks like the vast majority is printing aaaaaaaaaaaaaaa...., from that one exec error test lol

Did we lose truncation of long strings or something?

[outer musk]

Did we ever have it? 🤔

[viscid storm]

Yeah, I mean ctrl-C'ing the tests used to exit quickly I think

But idk now that you mention it, maybe I've never done that with the verbosity tuned up

[outer musk]

it might just be the verbosity yeah - it respects whatever last setting you had it in

though I would not be shocked if something about interrupting regressed

possibly two separate issues

[viscid storm]

Yeah I guess the concerning part is that it's uninterruptable. But I wouldn't be surprised if this is only noticeable when you have ridiculously long stdout/stderr strings and tuned the verbosity up, in which case it's pretty obscure

[outer musk]

if you ctrl+c again it should exit immediately

first one sends an interrupt, second one is the frontend just going "welp ok then" and exiting