You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But it does not make it clear from the log or from the end output what passed. I don't think it needs to list out all of the passing tests at the end, as in most cases this will just be noise, but when run with -v I think spread should indicate something in the log that can be grepped for to tell that a test passed, for example from the above run we had:
(with lots of other tests interspersed in the actual output, the above was filtered for just lines related to the test google-nested:ubuntu-20.04-64:tests/nested/classic/hotplug)
it would be nice if after a test passed it had something like
Spread makes it very obvious what things failed:
But it does not make it clear from the log or from the end output what passed. I don't think it needs to list out all of the passing tests at the end, as in most cases this will just be noise, but when run with
-v
I think spread should indicate something in the log that can be grepped for to tell that a test passed, for example from the above run we had:(with lots of other tests interspersed in the actual output, the above was filtered for just lines related to the test
google-nested:ubuntu-20.04-64:tests/nested/classic/hotplug
)it would be nice if after a test passed it had something like
or the
Success executing
line could even be combined withRestoring
to be something like:Basically something that makes it easy to grep a verbose log to tell:
Again, this doesn't need to be in the default output, the verbose output is enough for our use cases I think.
The text was updated successfully, but these errors were encountered: