Issue 760793003: Push roll candidates based on candidate ref instead of lkgr.

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 760793003: Push roll candidates based on candidate ref instead of lkgr. (Closed)

Created:
6 years ago by Michael Achenbach

Modified:
6 years ago

Reviewers:
Paweł Hajdan Jr., Jakob Kummerow

CC:
v8-dev

Base URL:
https://chromium.googlesource.com/v8/v8.git@master

Project:
v8

Visibility:
Public.

Push roll candidates based on candidate ref instead of lkgr. This pushes v8 to the candidates branch based on the candidate ref, which is guaranteed to be the same for 8 hours. The candidate ref is maintained by this bot: http://build.chromium.org/p/client.v8/builders/Auto-roll%20-%20release%20process NOTRY=true BUG=chromium:431669 LOG=n

Created: 6 years ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+13 lines, -14 lines)			Patch
	M	tools/push-to-trunk/auto_push.py	View		4 chunks	+9 lines, -10 lines	0 comments	Download
	M	tools/push-to-trunk/test_scripts.py	View		3 chunks	+4 lines, -4 lines	0 comments	Download

Total messages: 8 (3 generated)

Michael Achenbach

PTAL. tandrii is my normal reviewer for v8-side scripts - but he is OOO.

6 years ago (2014-11-26 11:46:55 UTC) #2

commit-bot: I haz the power

CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/760793003/1

6 years ago (2014-11-26 15:23:32 UTC) #7

Message was sent while issue was closed.

Committed patchset #1 (id:1)