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
To make tests pass when there are problems with teardown, I added a broad exception catcher that just logs errors when teardowns fail. There are two issues with this:
(a) failed deletions mean that datasets will collect in the testing project
(b) if something's consistently failing it won't show up in the test logs unless the test happens to fail, since bazel suppresses all non-failing test logs
I don't really know what a good solution is so I'm filing this issue to deal with it later.
The text was updated successfully, but these errors were encountered:
To make tests pass when there are problems with teardown, I added a broad exception catcher that just logs errors when teardowns fail. There are two issues with this:
(a) failed deletions mean that datasets will collect in the testing project
(b) if something's consistently failing it won't show up in the test logs unless the test happens to fail, since bazel suppresses all non-failing test logs
I don't really know what a good solution is so I'm filing this issue to deal with it later.
The text was updated successfully, but these errors were encountered: