Skip to content

[libc] Temporarily disable LlvmLibcFileTest.WriteOnly in libc.test.src.__support.File.file_test.__hermetic__ due to precommit bots's consistent failures. #128186

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 6 commits into from
Closed

[libc] Temporarily disable LlvmLibcFileTest.WriteOnly in libc.test.src.__support.File.file_test.__hermetic__ due to precommit bots's consistent failures. #128186

Changes from 2 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
6ce3f46
[libc] Temporarily disable LlvmLibcFileTest.WriteOnly in libc.test.sr…
lntue Feb 21, 2025
6c72474
Apply comment.
lntue Feb 21, 2025
f55e5f6
New file test failure.
lntue Feb 21, 2025
101ba37
Try to set the test hermetic only in full build mode.
lntue Feb 21, 2025
90b1245
Remove x86_64 check because the precommit failed in aarch64.
lntue Feb 21, 2025
8228342
Change to UNIT_TEST_ONLY.
lntue Feb 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions libc/test/src/__support/File/file_test.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,6 +113,9 @@ StringFile *new_string_file(char *buffer, size_t buflen, int bufmode,
LIBC_NAMESPACE::File::mode_flags(mode));
}

// TODO: Investigate the precommit bots' failures of this test and re-enable it.
Copy link
Contributor

@jhuber6 jhuber6 Feb 21, 2025

Choose a reason for hiding this comment

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

Use

#if 0
...
#endif

Copy link
Contributor Author

@lntue lntue Feb 21, 2025

Choose a reason for hiding this comment

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

Done.

Copy link
Member

@petrhosek petrhosek Feb 21, 2025

Choose a reason for hiding this comment

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

Google Test supports disabling tests by prefixing their name with DISABLED_. This is better than commenting out the code or using #if 0, as disabled tests are still compiled (and thus won't rot). We should consider implementing the same feature in libc's test framework.

Copy link
Contributor

@jhuber6 jhuber6 Feb 21, 2025

Choose a reason for hiding this comment

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

We'd probably want that to be target dependent as well, there's a handful of places where I need to disable a test only on NVPTX for example.

// https://github.com/llvm/llvm-project/issues/128185.
#if 0
TEST(LlvmLibcFileTest, WriteOnly) {
const char data[] = "hello, file";
constexpr size_t FILE_BUFFER_SIZE = sizeof(data) * 3 / 2;
Expand Down Expand Up @@ -150,6 +153,7 @@ TEST(LlvmLibcFileTest, WriteOnly) {

ASSERT_EQ(f->close(), 0);
}
#endif

TEST(LlvmLibcFileTest, WriteLineBuffered) {
const char data[] = "hello\n file";
Expand Down
Loading