Issue 23619035: Temporarily disabling Git checkout tests.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 23619035: Temporarily disabling Git checkout tests. (Closed)

Created:
7 years, 3 months ago by rmistry

Modified:
7 years, 3 months ago

Reviewers:
M-A Ruel

CC:
chromium-reviews, Dirk Pranke, cmp-cc_chromium.org, M-A Ruel, iannucci+depot_tools_chromium.org, ilevy-cc_chromium.org, skiabot_google.com

Base URL:
http://src.chromium.org/svn/trunk/tools/depot_tools/

Visibility:
Public.

Description

Temporarily disabling Git checkout tests. Disabling due to the unrelated presubmit failures in https://chromiumcodereview.appspot.com/24047003/. Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=222766

Patch Set 1 #

Created: 7 years, 3 months ago

		Unified diffs	Side-by-side diffs	Stats (+4 lines, -4 lines)
	M	tests/checkout_test.py	View	1 chunk	+4 lines, -4 lines	0 comments

Messages

Total messages: 5 (0 generated)

Expand Messages | Collapse Messages

commit-bot: I haz the power

CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/rmistry@google.com/23619035/1

7 years, 3 months ago (2013-09-12 12:05:49 UTC) #3

rmistry

7 years, 3 months ago (2013-09-12 12:26:19 UTC) #5

Message was sent while issue was closed.

Thanks Marc-Antoine.

Is there any way for me to get temporary access to a CQ machine that runs these
presubmit scripts, I have not been able to reproduce the failure locally or on a
GCE instance.

I could make a few guesses and try to fix it but it will be a lot easier if I
had access to the machine where it fails.

Expand Messages | Collapse Messages