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
There is a bug today where doing bazel run will pass, but not remove the stale snapshot. If you run bazel test, the snapshot will be marked as stale. To keep parity with jest, I would expect bazel run to clean out the the source tree when a file is missing. Generated files test can do this today, so I would expect after a snapshot run to use a generated files test like write_source_files to remove deleted files.
Version
Development (host) and target OS/architectures:
Output of bazel --version: 6.2.0
Version of the Aspect rules, or other relevant rules from your WORKSPACE or MODULE.bazel file:
0.19 - rules_jest
Language(s) and/or frameworks involved:
How to reproduce
`bazel run` a test target that produces a snapshot. Change the name of the file that produces the snapshot and run it again. It will pass. Run `bazel test` and you will see info that says there is an obsolete snapshot
What happened?
There is a bug today where doing
bazel run
will pass, but not remove the stale snapshot. If you runbazel test
, the snapshot will be marked as stale. To keep parity with jest, I would expectbazel run
to clean out the the source tree when a file is missing. Generated files test can do this today, so I would expect after a snapshot run to use a generated files test likewrite_source_files
to remove deleted files.Version
Development (host) and target OS/architectures:
Output of
bazel --version
: 6.2.0Version of the Aspect rules, or other relevant rules from your
WORKSPACE
orMODULE.bazel
file:0.19 - rules_jest
Language(s) and/or frameworks involved:
How to reproduce
Any other information?
jest_test
is passing-u
so that's good ✅ https://github.com/aspect-build/rules_jest/blob/main/jest/private/jest_test.bzl#L96rules_jest/jest/private/bazel_snapshot_resolver.cjs
Line 67 in e3914b7
The text was updated successfully, but these errors were encountered: