New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 682704 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
█ xunji...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

cronet_test_instrumentation_apk failing on chromium.android/Android Cronet Lollipop Builder

Project Member Reported by jbudorick@chromium.org, Jan 19 2017 
cronet_test_instrumentation_apk failing on chromium.android/Android Cronet Lollipop Builder

Type: build-failure

Builders failed on: 
- Android Cronet Lollipop Builder: 
  https://build.chromium.org/p/chromium.android/builders/Android%20Cronet%20Lollipop%20Builder


Failing with:

I  105.508s run_tests_on_device(0accb4ed43e4b057)  detected failure in org.chromium.net.CronetUrlRequestTest#testBadMethod. raw output:
I  105.508s run_tests_on_device(0accb4ed43e4b057)    INSTRUMENTATION_ABORTED: System has crashed.

Logcat is attached.
testBadMethod_system_crash_logcat.txt
108 KB View Download

Comment 1 by xunji...@chromium.org, Jan 19 2017

Cc: xunji...@chromium.org
Labels: -Pri-1 Pri-2
This might be a device flake. The crash is in libart. I will keep an eye on it.


4b057:  01-19 16:05:17.046 18279 18279 I test_runner_py: START org.chromium.net.CronetUrlRequestTest#testBadMethod 

Stack Trace:
  RELADDR   FUNCTION                                                                                                                          FILE:LINE
  00004e64  UnwindCurrent::Unwind(unsigned int, ucontext*)+23                                                                                 /system/lib/libbacktrace_libc++.so
  00003665  Backtrace::Unwind(unsigned int, ucontext*)+8                                                                                      /system/lib/libbacktrace_libc++.so
  00256429  art::DumpNativeStack(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, int, char const*, art::mirror::ArtMethod*)+84  /system/lib/libart.so
  00238fe7  art::Thread::Dump(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) const+158                                         /system/lib/libart.so
  0022881d  art::AbortState::DumpThread(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, art::Thread*)+32                        /system/lib/libart.so
  00228a87  art::AbortState::Dump(std::__1::basic_ostream<char, std::__1::char_traits<char> >&)+354                                           /system/lib/libart.so
  00228c7f  art::Runtime::Abort()+82                                                                                                          /system/lib/libart.so
  000a7371  art::LogMessage::~LogMessage()+1360                                                                                               /system/lib/libart.so
  00160ff5  art::IndirectReferenceTable::AbortIfNoCheckJNI()+72                                                                               /system/lib/libart.so
  00239b37  art::Thread::DecodeJObject(_jobject*) const+634                                                                                   /system/lib/libart.so
  001baad9  art::JNI::IsSameObject(_JNIEnv*, _jobject*, _jobject*)+304                                                                        /system/lib/libart.so
  00087d9b  DeathRecipientList::find(_jobject*)+56                                                                                            /system/lib/libandroid_runtime.so
  00087f0f  ???                                                                                                                               /system/lib/libandroid_runtime.so
  0009a36f  Java_android_os_BinderProxy_unlinkToDeath__Landroid_os_IBinder_00024DeathRecipient_2I+106                                         /data/dalvik-cache/arm/system@framework@boot.oat

Comment 2 by xunji...@chromium.org, Jan 20 2017

Status: WontFix (was: Available)
Seems to be indeed a device flake. Last 30 runs are green.

Comment 3 by jbudorick@chromium.org, Jan 20 2017 

Thanks for watching it!
►

Sign in to add a comment