Janak Ramakrishnan

Does the flag `--build_tests_only` work to make Bazel behave as you expect in this case?

I think the correctness is pretty good, since it uses inodes. However, does Windows have inodes? Also, I'm confused by this report, since the flag is not intended to help...

Ah, wasn't thinking. Yes, that could be it. But I think Windows [doesn't have a node id]( https://github.com/bazelbuild/bazel/blob/14292d176cb85d1cf6e20f79fde0249b0fe6ba24/src/main/java/com/google/devtools/build/lib/windows/WindowsFileSystem.java#L203). So we're down to [mtime and size]( https://github.com/bazelbuild/bazel/blob/14292d176cb85d1cf6e20f79fde0249b0fe6ba24/src/main/java/com/google/devtools/build/lib/vfs/DigestUtils.java#L70-L75), which have been historically...

cc @susinmotion @alexjski

@alexjski could you take the lead on this? Thanks!

Looks like this is only an issue with native tests, passing over to server rules team to make a policy decision. Hopefully this problem goes away since Starlark doesn't use...

I think it's the opposite: in a Starlark action, you can set the environment to whatever you like via the `env` parameter of `actions.run.` I'll defer to the rules team...

Thanks for the quick response! The immediate problem this is causing me is that `cy.document()((doc) => doc.createElement('input'))` does not produce an `HTMLElement`. My production code (and dependent libraries) interact with...

My concern isn't the window per se, it's more about having to change all production code to use an injected document (or window) rather than the global `document` or `window`,...

It would be helpful to have a note in the tutorials that they are outdated, even if it's too much work to update them right now. I was also unable...