Jacob MacDonald

> produced a Cannot call test() after tests have started error - I think it's because it was called after an await. This happens if `test` is called after the...

> This isn't good though - if there's no way to suppress this (@jakemac53?) then we might have to switch back to handling it locally and just not calling group/test...

> When I run tests and one fails, I don't want to dig through 1000+ lines of spam to find the failure message :-P I am not saying it shouldn't...

@scheglov do you know if you are using the expanded reporter also? If you are seeing spam for passed tests it indicates you are probably not getting the compact reporter....

The default reporter is the compact reporter when using the test runner, if you are just directly invoking the test files though then maybe that is the code path you...

Good point about enhanced parts, that would be a nice way to do this in the future

Makes sense, iirc the glob support does have some support for caching globs that are the same and ran in the same phase. So we might be able to do...

If/when we have an alternative entry point to the compilers, we would be happy to use it. I mentioned in the other PR, but if we also can commit to...

cc @nshahan are we committing to the current CLI args as well as a part of this?

@a-siva note that we also have a dependency on the frontend server path so if we want to fully stop relying on SDK internals we also would need a public...