"gclient (with patch)" is flaky |
||
Issue description"gclient (with patch)" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is not infrastructure-related (e.g. flaky test), please add Sheriff-Chromium label and change issue status to Untriaged. When done, please remove the issue from Trooper Bug Queue by removing the Infra-Troopers label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRnY2xpZW50ICh3aXRoIHBhdGNoKQw. The chromium-try-flakes app is able to file bugs for individual tests when the test launcher is uploading results to the Test Results Server. If recent flakes above are caused by failing tests and you would like to have them filed as invidual bugs, please read more at https://goo.gl/QJKXV4. This flaky test/step was previously tracked in issue 838976 .
,
May 31 2018
#1 probably doesn't make sense, since the error actually happens within the same gclient process. So gclient itself runs under the wrong python? That would fail a lot sooner:
$ python3 -m venv ~/virtualenv/py3.5
$ source ~/virtualenv/py3.5/bin/activate
(py3.5) $ python --version
Python 3.5.3
(py3.5) $ gclient sync
Traceback (most recent call last):
File "/usr/local/google/home/sergeyberezin/code/depot_tools/gclient.py", line 99, in <module>
import urlparse
ImportError: No module named 'urlparse'
So that's not it... But how can it possibly fail then?
,
May 31 2018
This error is also truly flaky: on the same bot (which I don't think reboots between builds): https://chromium-swarm.appspot.com/task?id=3dcb2a59f3fd8f10 (failed and reported) https://chromium-swarm.appspot.com/task?id=3dcb3187fc265310 (next build on the same bot, passed) Same thing happens on Linux in golo or ccompute (I can't confirm it for windows).
,
May 31 2018
I can't think of a way to debug this for now, so closing as won't fix. Hopefully it's rare enough. |
||
►
Sign in to add a comment |
||
Comment 1 by sergeybe...@chromium.org
, May 30 2018These all fail with: File "/b/swarming/w/ir/cipd_bin_packages/lib/python2.7/pickle.py", line 977, in load_string self.append(rep.decode("string-escape")) LookupError: unknown encoding: string-escape The previous bug simply mentions that the hosts must be "really hosed", and rebooting usually helps. Google search turned up this error mostly in cases when a Python 2.7 code was mistakenly run with a Python 3.* interpreter. This doesn't seem to be the case here, but who knows? Maybe the subprocess accidentally picks up system Python 3?