Skip to content

Conversation

@sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Dec 19, 2024

This test was recently added in #23136 but the test fails on windows due to errno mismatch. See #8882.

This test was recently added in emscripten-core#23136 but the test fails on windows
due to errno mismatch.  See emscripten-core#8882.
@sbc100 sbc100 requested review from dschuff and hoodmane December 19, 2024 02:42
@sbc100
Copy link
Collaborator Author

sbc100 commented Dec 19, 2024

Landing TBR to unblock the roller.

@sbc100 sbc100 merged commit 0186a3f into emscripten-core:main Dec 19, 2024
16 of 29 checks passed
@sbc100 sbc100 deleted the disable_test branch December 19, 2024 03:29
self.do_runf('fs/test_fs_rename_on_existing.c', 'success')

@also_with_nodefs_both
@crossplatform
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does @crossplatform do? I had assumed that it wouldn't run on windows if we didn't include @crossplatform. Does it add crossplatform tests to the PR CI? And they are always run on the main branch?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's slightly subtle. the actual @crossplatform decorator just marks the test as being a test that might have different behavior across platforms, and we run those tests on Mac and Windows on the CI that runs on Github (we run only those test to keep CI times costs down). But the builders we use to build the EMSDK releases (which run on chromium's CI infrastructure) do run all of the 'other' and some of the core test suites on Mac and Windows. So that's why we've been catching these failures after they've already landed in the emscripten repo. Usually it works fine, but you've hit basically the one area of work where it's an annoyance. :) Probably for these kinds of tests you should either mark them @crossplatform or explicitly disable them on Windows. As for how much effort you should put in, noderawfs has always sort of been "best-effort" on Windows. Maybe we should try to come up with a better-defined policy, but maybe for now a decent tradeoff would be to start by trying out your tests as crossplatform and if it's not too much effort to make them work, do that, and otherwise just disable on Windows?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants