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
{{ message }}
This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
Is buck caching the test results? If yes, how can I see which of those test results were cached, and which of them did actually run?
I see here that buck used to have some options related to test result cache back in 2016, but they were removed in 2017 here. I am not sure why, as there is no changelog neither release notes that I can refer to. Any idea?
Thanks!
The text was updated successfully, but these errors were encountered:
Buck's test caching was removed in 2017 just as you mentioned, allegedly because (quote) "People wrote really bad tests that weren't deterministic, and didn't realize that their tests weren't actually running. afaik we removed it because of this, and we should run all tests every time".|
Such a pity, I also think as commented in 0fc321f#commitcomment-22227138 that test result caching is one of the main reasons to use a build system like buck/bazel.
Hello:
I am using buck and also bazel to run the same set of tests (in here). When running them with bazel, the output is as follows:
As you can see, it clearly indicates which of the test results were cached and which of them did run.
With buck I get the following output:
Is buck caching the test results? If yes, how can I see which of those test results were cached, and which of them did actually run?
I see here that buck used to have some options related to test result cache back in 2016, but they were removed in 2017 here. I am not sure why, as there is no changelog neither release notes that I can refer to. Any idea?
Thanks!
The text was updated successfully, but these errors were encountered: