This particular test relies on internal details from the libc++
filesystem implementation header, and those details are structured
differently in the implementation for windows.
Details
- Reviewers
curdeius Mordante - Group Reviewers
Restricted Project - Commits
- rGec402f1d5da0: [libcxx] [test] Explain an XFAIL LIBCXX-WINDOWS-FIXME and convert into…
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
libcxx/test/libcxx/input.output/filesystems/class.directory_entry/directory_entry.mods/last_write_time.pass.cpp | ||
---|---|---|
16 | Your patch description said that it was going to be converted into UNSUPPORTED, right? |
libcxx/test/libcxx/input.output/filesystems/class.directory_entry/directory_entry.mods/last_write_time.pass.cpp | ||
---|---|---|
16 | Oh, right. What do you think, which marking would be better here? |
libcxx/test/libcxx/input.output/filesystems/class.directory_entry/directory_entry.mods/last_write_time.pass.cpp | ||
---|---|---|
16 | No strong feelings here. I'd probably go for unsupported. Your comment clearly explains why it is so IMO. Also, unless you think it will change in a foreseeable future, it makes no sense to me to XFAIL. |
Some small nits other than that LGTM. The UNSUPPORTED change shouldn't break anything, but please keep eye out. Alternatively give it another CI run and land it after the build passes.
libcxx/test/libcxx/input.output/filesystems/class.directory_entry/directory_entry.mods/last_write_time.pass.cpp | ||
---|---|---|
13 | Please capitalize Windows. | |
16 | Reading the comment I think UNSUPPORTED would be better. |
Please capitalize Windows.