New issue
Advanced search Search tips

Issue 598881 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Presubmit to build.git always times out

Project Member Reported by dimu@chromium.org, Mar 29 2016

Issue description

I'm trying to submit my CL at https://chromereviews.googleplex.com/383317014/ but the presubmit times out after 20mins, so I created a test CL (https://chromereviews.googleplex.com/386207013/) submitting only an empty line), which times out as well.






 
Status: Available (was: Untriaged)
This is still timing out.
Looks like it's hanging on this line:

DEBUG:root:/mnt/data/b/build/slave/build-internal-presubmit/build/build_internal/scripts/slave-internal/bling/init_device_test.py --verbose;  cwd=/mnt/data/b/build/slave/build-internal-presubmit/build/build_internal


Comment 3 by d...@chromium.org, Mar 30 2016

Filling in context from the thread that inspired this bug:

That test is *not* the problem. A bunch of things run in parallel, and that specific one takes <1 second.

The actual issue here is probably a bug in pylint, which is run in all Python files in the archive. The bug is that it hangs forever. Running on my much-more-powerful local machine, the Pylint line still hangs forever.

I haven't spent the time to delve deeper, nor do I have time to spend on this issue, but that's where I left it.
link to thread?

Comment 6 by dimu@chromium.org, Mar 30 2016

Is it possible to disable pylint for now?
Project Member

Comment 7 by bugdroid1@chromium.org, Apr 2 2016

The following revision refers to this bug:
  http://goto.ext.google.com/viewvc/chrome-internal?view=rev&revision=86054

------------------------------------------------------------------
r86054 | dnj@google.com | 2016-04-02T15:42:18.420899Z

-----------------------------------------------------------------

Comment 8 by d...@chromium.org, Apr 2 2016

Owner: d...@chromium.org
Status: Started (was: Available)
I spent a few this morning looking deeper into this issue and I think I have resolved it. I'm going to go ahead and re-submit your main CL and close your whitespace one for the true test.

Comment 9 by d...@chromium.org, Apr 2 2016

Status: Verified (was: Started)
Your CL successfully submitted, so I'm going to close this as Verified.

Comment 10 by dimu@chromium.org, Apr 4 2016

Thank you so much for fixing it dnj@

Sign in to add a comment