blink_heap_unittests failing on chromium.webkit/WebKit Android (Nexus4) |
|||||||||
Issue descriptionblink_heap_unittests failing on chromium.webkit/WebKit Android (Nexus4) Builders failed on: - WebKit Android (Nexus4): https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Android%20%28Nexus4%29 stdout: -------------------------------- 8< -------------------------------- E 20.149s Main Unrecognized error occurred. Traceback (most recent call last): File "/b/c/b/WebKit_Android__Nexus4_/src/build/android/test_runner.py", line 913, in main return RunTestsCommand(args) File "/b/c/b/WebKit_Android__Nexus4_/src/build/android/test_runner.py", line 672, in RunTestsCommand return RunTestsInPlatformMode(args) File "/b/c/b/WebKit_Android__Nexus4_/src/build/android/test_runner.py", line 777, in RunTestsInPlatformMode with json_writer, logcats_uploader, env, test_instance, test_run: File "/b/c/b/WebKit_Android__Nexus4_/src/build/android/pylib/base/test_run.py", line 39, in __enter__ self.SetUp() File "/b/c/b/WebKit_Android__Nexus4_/src/build/android/pylib/local/device/local_device_gtest_run.py", line 316, in SetUp self._test_instance.GetDataDependencies()) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/utils/parallelizer.py", line 236, in pMap r.pFinish(None) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/utils/parallelizer.py", line 135, in pFinish self._objs.JoinAll() File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/utils/reraiser_thread.py", line 186, in JoinAll self._JoinAll(watcher, timeout) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/utils/reraiser_thread.py", line 158, in _JoinAll thread.ReraiseIfException() File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/utils/reraiser_thread.py", line 81, in run self._ret = self._func(*self._args, **self._kwargs) File "/b/c/b/WebKit_Android__Nexus4_/src/build/android/pylib/local/device/local_device_environment.py", line 59, in wrapper return f(dev, *args, **kwargs) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function return func(*args, **kwargs) File "/b/c/b/WebKit_Android__Nexus4_/src/build/android/pylib/local/device/local_device_gtest_run.py", line 312, in individual_device_set_up step() File "/b/c/b/WebKit_Android__Nexus4_/src/build/android/pylib/local/device/local_device_gtest_run.py", line 288, in push_test_data delete_device_stale=True) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/android/decorators.py", line 57, in timeout_retry_wrapper retry_if_func=retry_if_func) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/utils/timeout_retry.py", line 159, in Run error_log_func=error_log_func) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/utils/reraiser_thread.py", line 186, in JoinAll self._JoinAll(watcher, timeout) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/utils/reraiser_thread.py", line 158, in _JoinAll thread.ReraiseIfException() File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/utils/reraiser_thread.py", line 81, in run self._ret = self._func(*self._args, **self._kwargs) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/utils/timeout_retry.py", line 152, in <lambda> child_thread = reraiser_thread.ReraiserThread(lambda: func(*args, **kwargs), File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/android/decorators.py", line 47, in impl return f(*args, **kwargs) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/android/device_utils.py", line 1286, in PushChangedFiles self._PushFilesImpl(host_device_tuples, all_changed_files) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/android/device_utils.py", line 1400, in _PushFilesImpl for h, _ in host_device_tuples) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/android/device_utils.py", line 1400, in <genexpr> for h, _ in host_device_tuples) File "/b/c/b/WebKit_Android__Nexus4_/src/third_party/catapult/devil/devil/utils/host_utils.py", line 10, in GetRecursiveDiskUsage running_size = os.path.getsize(path) File "/usr/lib/python2.7/genericpath.py", line 49, in getsize return os.stat(filename).st_size OSError: [Errno 2] No such file or directory: '/b/c/b/WebKit_Android__Nexus4_/src/out/Release/gen/services/resource_coordinator/manifest.json' step returned non-zero exit code: 1 -------------------------------- 8< --------------------------------
,
Apr 28 2017
,
Apr 28 2017
The revert for https://codereview.chromium.org/2798713002/ may also fix this bug. Leaving sheriff label for now just to keep an eye on this.
,
May 1 2017
Looks like the revert mentioned in #3 has removed the blink_heap_unittests failure. Removing sheriff label now. Adding the Speed component as best guess, since that's the component on the bug referenced by the reverted CL. oysteine: Please change components as appropriate.
,
May 2 2017
+nednguyen: From looking at the callstack, it looks like something in Catapult doesn't handle files which are newly added and only present on the host, not the device? (The .manifest was added in the CL linked above). Any ideas?
,
May 2 2017
+JOhn who is the owner of devil/
,
May 2 2017
Don't add files in <output directory>/gen to data in gn targets. gen/ does not survive the builder->tester transfer. The file you're looking for isn't present on the host, either.
,
May 2 2017
... or in this case, data_deps on a service_manifest target.
,
May 2 2017
#8 Ah thanks, that makes sense. Does that mean data_deps is only used for Android? Those were the only targets failing this (there were also nothing failing in the CQ).
,
May 2 2017
No, but it likely means there's a difference in how the tests are triggered & how dependencies are transferred. I'm guessing the desktop bots isolate the tests on the builders?
,
May 2 2017
+bsheedy who was chrome sheriff at the time: You said the file was present on the host side when you tested this locally right? (I've been trying and failing to repro this myself but it's been a while since I've ran Android tests locally).
,
May 2 2017
You likely would not be able to reproduce this locally w/o running https://codesearch.chromium.org/chromium/build/scripts/slave/zip_build.py
,
May 2 2017
Yes, when I built locally, the file was present in gen/services/resource_coordinator, but the packaged build from our FYI bot did not have it. (Also, not a sheriff, just someone whose bot was failing)
,
May 3 2017
,
May 3 2017
About to reland this; I'm pretty sure I have the data_deps issue fixed, but it's not something I've been able to repro on any trybot (including perf trybots), and reproing locally seems to require a full buildbot setup.
,
May 3 2017
Problem doesn't seem to be fixed, at least not on our FYI bot https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.fyi%2FAndroid_VR_Tests%2F7202%2F%2B%2Frecipes%2Fsteps%2Fvr_shell_unittests%2F0%2Fstdout
,
May 3 2017
Curses. I'll revert the CL; looks like I have to replicate a full buildbot setup on my local machine just to repro this in any way before landing it then, that's pretty unfortunate.
,
May 3 2017
#18: let's talk before you do that. I'll be up in your neck of the woods tomorrow.
,
May 3 2017
#19: Great, thank you!
,
May 5 2017
Relanding now; thanks to jbudorick for helping me figuring out the issue yesterday.
,
May 7 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
,
Jan 11
Setting defect without priority to Pri-2. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by rogerta@chromium.org
, Apr 28 2017