From 4f35c7d45953a631b3078b1c8def0d6e380182e6 Mon Sep 17 00:00:00 2001 From: Tobias Thierer Date: Wed, 3 Aug 2016 19:12:37 +0100 Subject: [PATCH] Update known buildbot failures for ProcessBuilderTest Also updated the comment string based on our latest understanding. This is a native crash. Both of the affected tests as well as the other tests in ProcessBuilderTest run 'sh' as a child process. Only one of the tests that are affected to far accesses /proc/, which had previously been suspected as related to the cause. The statement that this is a native crash is based on there not being a relevant stacktrace in logcat. A 'sh' related native crash failure occurs in the logs but that is not specific to these tests so it's not clear if it is related. If not, it's not clear why the additional native crash doesn't show up in the logs. Test: Nothing Bug: 30657148 Change-Id: I8347edab3cacd060baf1087a1939926f70fdd349 --- tools/libcore_failures.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/tools/libcore_failures.txt b/tools/libcore_failures.txt index bf8d12b9c..094f8bf6f 100644 --- a/tools/libcore_failures.txt +++ b/tools/libcore_failures.txt @@ -262,10 +262,12 @@ names: ["org.apache.harmony.tests.java.lang.ProcessTest#test_destroyForcibly"] }, { - description: "Flaky failure, possibly caused by a kernel bug accessing /proc/", + description: "Flaky failure, native crash in the runtime. + Unclear if this relates to the tests running sh as a child process.", result: EXEC_FAILED, - bug: 27464570, + bug: 30657148, modes: [device], - names: ["libcore.java.lang.ProcessBuilderTest#testRedirectInherit"] + names: ["libcore.java.lang.ProcessBuilderTest#testRedirectInherit", + "libcore.java.lang.ProcessBuilderTest#testRedirect_nullStreams"] } ] -- 2.11.0