[libc] disable flakey tests
The mprotect test has been failing and causing significant buildbot noise. Given that this is a simple functions it's more important that the buildbot errors be useful than having more thorough tests for this function. Reviewed By: sivachandra, lntue Differential Revision: https://reviews.llvm.org/D138061
This commit is contained in:
parent
0e1708ff64
commit
c46a465eb9
|
@ -43,6 +43,9 @@ TEST(LlvmLibcMProtectTest, NoError) {
|
|||
EXPECT_THAT(__llvm_libc::munmap(addr, alloc_size), Succeeds());
|
||||
}
|
||||
|
||||
// This test is disabled currently due to flakeyness. It will be re-enabled once
|
||||
// it is less flakey.
|
||||
/*
|
||||
TEST(LlvmLibcMProtectTest, Error_InvalidWrite) {
|
||||
// attempting to write to a read-only protected part of memory should cause a
|
||||
// segfault.
|
||||
|
@ -60,3 +63,4 @@ TEST(LlvmLibcMProtectTest, Error_InvalidWrite) {
|
|||
// Reading from a write only segment may succeed on some platforms, so there's
|
||||
// no test to check that.
|
||||
}
|
||||
*/
|
||||
|
|
Loading…
Reference in New Issue