- 07 Feb, 2018 4 commits
-
-
Tom Anderson authored
BUG=807986 R=dpranke Change-Id: I6b7e94d489a228c5dde23a9b6c7d6f58ce73b180 Reviewed-on: https://chromium-review.googlesource.com/905285Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
-
recipe-roller authored
This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (e.g. depot_tools) into downstream projects (e.g. tools/build). More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. recipe_engine: https://crrev.com/b80999e32c0692d0ab2fe00722c2550f8b74c0ac raw_io: fix to use splitlines for add_output_log (tikuta@google.com) TBR=iannucci@chromium.org Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: Ia4b2f1c2d20e4e8f511cc12cc8fca9391382a42e Reviewed-on: https://chromium-review.googlesource.com/905593Reviewed-by: Recipe Roller <recipe-roller@chromium.org> Commit-Queue: Recipe Roller <recipe-roller@chromium.org>
-
Andrii Shyshkalov authored
This reverts commit fa573785. Reason for revert: broke CQ on branches. Example: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/chromium_presubmit/28220 Original change's description: > bot_update: allow rebasing the patch onto an older revision. > > When applying a rebase, we normally go from an older base commit to a newer one. > > A ---- B ---- C ---- D -origin/master > \ > E -branch > > In this case, `git rebase D` would certainly work as expected. However, > writing `git rebase B` would NOT get us to the following state: > > A ---- B ---- C ---- D -origin/master > \ > E' -branch > > In fact, it would have no effect. > > This article http://matthew-brett.github.io/pydagogue/rebase_without_tears.html > explains the general invocation as > > `git rebase --onto <graft-point> <exclude-from> <include-from>` > > If you don’t specify --onto, <graft-point> defaults to <exclude-from> > > So what's happening is, by writing `git rebase B` we're rebasing onto B, > excluding commits that are in B. Commit C is not "in" B so it is kept and we're > back to the starting point. > > So I suggest to change the invocation to `git rebase --onto B origin/master`, > which rebases onto B, excluding commits that are in origin/master. This works > more generally and allows rebasing "backwards". > > Bug: None > Change-Id: I68e4d805811530b585550bc75099354fef4e9c15 > Reviewed-on: https://chromium-review.googlesource.com/904004 > Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> > Commit-Queue: Oleh Prypin <oprypin@chromium.org> TBR=iannucci@chromium.org,tandrii@chromium.org,oprypin@chromium.org Change-Id: I7243641d84428bf4504ee798bf31ad0afbfd4865 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: None Reviewed-on: https://chromium-review.googlesource.com/905862 Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
-
Robert Iannucci authored
R=tandrii@chromium.org, vadimsh@chromium.org Bug: 809645 Change-Id: I21ad49fa03630955eca6ecd531445bc4acf0c0c6 Reviewed-on: https://chromium-review.googlesource.com/905822Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
-
- 06 Feb, 2018 7 commits
-
-
Robert Iannucci authored
This will be used when running infrastructure code locally (e.g. recipes) to correctly interact with LUCI service APIs (such as luci-scheduler.appspot.com). It is also generically useful to explore and interact with LUCI service APIs on the command line (for debugging/scripting). R=tandrii@chromium.org, vadimsh@chromium.org Bug: 808677 Change-Id: I41cfd4cc7e2d245d3a5d2be83f9879f92a8d1bca Reviewed-on: https://chromium-review.googlesource.com/905457 Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
-
Andrii Shyshkalov authored
Goal: reduce number of git fetches from remote to the minimum possible. Minimum possible is either: * 0 if desired revision is pinned (!= HEAD) and already exists in cache * 1 if desired revision is HEAD * >= 2 if revision is pinned but we talk temporarily out-of-date git server not yet having it. This CL achieves the above. No fetch: https://ci.chromium.org/swarming/task/39dad20230c84110?server=chromium-swarm.appspot.com bot_update takes <1min, but it used to take at least 2. The steps are now like this: ... ===Running git cat-file -e 33bf8a94dcd5e0abbdf83e4afaed24b5180e3eb2=== In directory: /b/swarming/w/ir/cache/git/chromium.googlesource.com-chromium-src ===Succeeded in 0.0 mins=== ===Running /b/swarming/w/ir/cipd_bin_packages/bin/python -u /b/swarming/w/ir/recipe-checkout-dir/depot_tools/git_cache.py exists --quiet --cache-dir /b/swarming/w/ir/cache/git https://chromium.googlesource.com/chromium/src.git=== In directory: /b/swarming/w/ir/cache/builder/linux /b/swarming/w/ir/cache/git/chromium.googlesource.com-chromium-src ===Succeeded in 0.0 mins=== ===Running git remote set-url origin /b/swarming/w/ir/cache/git/chromium.googlesource.com-chromium-src=== In directory: /b/swarming/w/ir/cache/builder/linux/src ===Succeeded in 0.0 mins=== ===Running git fetch origin=== In directory: /b/swarming/w/ir/cache/builder/linux/src From /b/swarming/w/ir/cache/git/chromium.googlesource.com-chromium-src 003eedbfee47..5210107a20e8 master -> origin/master ===Succeeded in 0.0 mins=== ===Running git checkout --force 33bf8a94dcd5e0abbdf83e4afaed24b5180e3eb2=== ... Fetch & success: https://ci.chromium.org/swarming/task/39db022b874ffd10?server=chromium-swarm.appspot.com Fetch & retry because missing rev: https://ci.chromium.org/swarming/task/39db04ce8b4b8910?server=chromium-swarm.appspot.com Fetch because rev=HEAD: https://ci.chromium.org/swarming/task/39db0c0dd5ab5d10?server=chromium-swarm.appspot.com This has already been adopted in gclient. Bug: Change-Id: Id99892b62719fdf3f7e6e59058986d1500384f8d Reviewed-on: https://chromium-review.googlesource.com/771591 Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Jao-ke Chin-Lee <jchinlee@chromium.org>
-
Tom Anderson authored
This CL adds target_cpu and target_cpu_only variables. The logic is: * If target_cpu is defined in .gclient, use it. Otherwise, initialize it as an empty list. * If not target_cpu_only, add the host arch to the list too. detect_host_arch.py is copied directly from the Chromium repo. BUG=807986 R=dpranke Change-Id: I27621cbc81ad6a844648525863b92ffdd3b1d03a Reviewed-on: https://chromium-review.googlesource.com/902441 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by: Dirk Pranke <dpranke@chromium.org>
-
Oleh Prypin authored
When applying a rebase, we normally go from an older base commit to a newer one. A ---- B ---- C ---- D -origin/master \ E -branch In this case, `git rebase D` would certainly work as expected. However, writing `git rebase B` would NOT get us to the following state: A ---- B ---- C ---- D -origin/master \ E' -branch In fact, it would have no effect. This article http://matthew-brett.github.io/pydagogue/rebase_without_tears.html explains the general invocation as > `git rebase --onto <graft-point> <exclude-from> <include-from>` > If you don’t specify --onto, <graft-point> defaults to <exclude-from> So what's happening is, by writing `git rebase B` we're rebasing onto B, excluding commits that are in B. Commit C is not "in" B so it is kept and we're back to the starting point. So I suggest to change the invocation to `git rebase --onto B origin/master`, which rebases onto B, excluding commits that are in origin/master. This works more generally and allows rebasing "backwards". Bug: None Change-Id: I68e4d805811530b585550bc75099354fef4e9c15 Reviewed-on: https://chromium-review.googlesource.com/904004Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Oleh Prypin <oprypin@chromium.org>
-
recipe-roller authored
This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (e.g. depot_tools) into downstream projects (e.g. tools/build). More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. recipe_engine: https://crrev.com/a262d9709414e7270ee617510bd720b19e229779 raw_io: add add_output_log option (tikuta@google.com) TBR=iannucci@chromium.org Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: Icac945216219b5cb33bff914bc6f312595c5c6bc Reviewed-on: https://chromium-review.googlesource.com/905482 Commit-Queue: Recipe Roller <recipe-roller@chromium.org> Reviewed-by: Recipe Roller <recipe-roller@chromium.org>
-
Michael Moss authored
BUG=783607 R=agable@google.com, dpranke@google.com Change-Id: I6989203a9e560930cc53254c566275a30d3bead3 Reviewed-on: https://chromium-review.googlesource.com/902168Reviewed-by: Aaron Gable <agable@chromium.org> Commit-Queue: Michael Moss <mmoss@chromium.org>
-
recipe-roller authored
This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (e.g. depot_tools) into downstream projects (e.g. tools/build). More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. recipe_engine: https://crrev.com/8f09f5f2571c4ec5b22269eb44e53742dfae29fb Add sleep to the time recipe module (mknyszek@google.com) TBR=iannucci@chromium.org Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: I1889cd049d05e3e400b5e3ccbac4b73273791ce7 Reviewed-on: https://chromium-review.googlesource.com/903282Reviewed-by: Recipe Roller <recipe-roller@chromium.org> Commit-Queue: Recipe Roller <recipe-roller@chromium.org>
-
- 05 Feb, 2018 1 commit
-
-
John Budorick authored
TBR=agable@chromium.org Bug: 789809 Change-Id: I4ede72a3584b23d01063e5cfa20401c921762b50 Reviewed-on: https://chromium-review.googlesource.com/900664Reviewed-by: John Budorick <jbudorick@chromium.org> Commit-Queue: John Budorick <jbudorick@chromium.org>
-
- 02 Feb, 2018 3 commits
-
-
recipe-roller authored
This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (e.g. depot_tools) into downstream projects (e.g. tools/build). More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. recipe_engine: https://crrev.com/c9374582f3cbe9b1e54eaa851b891de56b7b7aa9 Add scheduler recipe module with EmitTrigger RPC support only. (tandrii@chromium.org) TBR=iannucci@chromium.org Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: Ibddefab48c94b9c034068cbe24b86dd46c85dc19 Reviewed-on: https://chromium-review.googlesource.com/900189 Commit-Queue: Recipe Roller <recipe-roller@chromium.org> Reviewed-by: Recipe Roller <recipe-roller@chromium.org>
-
Aaron Gable authored
R=maruel Change-Id: I0a5a18d598632bc77a8c70a21c8b3c4c2223d543 Reviewed-on: https://chromium-review.googlesource.com/899682Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Aaron Gable <agable@chromium.org>
-
Michael Achenbach authored
The first call to gsutil causes a network call and makes the download script slow also in the most optimal cases. This CL refactors the download script and moves the first gsutil call after checking locally if sha1s match. 1) This turns the input acquisition into a generator and buffers the files and sha1s in a list before multithreading. 2) This sequentially checks the sha1s and files and bails out early if all match. In Chrome-land, we usually call this script with only one file. There are some cases with around 4. This could also be parallelized if the need arises. 3) The initial gsutil check, which ensures gsutil is updated, is moved right in front of the multithreaded downloads. The performance of one call to download_from_google_storage for an existing 500MB file is 2.3s before this CL and 1.2s after (most of the remaining time left is spent for making sha1sum). Example for full gclient runhooks (when everything is up-to-date): Chromium: 32s before, 12s after V8: 12s before, 3s after Bug: 776311 Change-Id: Ia7715a6af84b1b336455ea88494d399bdb050317 Reviewed-on: https://chromium-review.googlesource.com/897562 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by: Ryan Tseng <hinoka@chromium.org>
-
- 01 Feb, 2018 5 commits
-
-
Sergey Berezin authored
Relevant commits: d4dc0c29a mac_toolchain: add support for legacy Xcode 8.* BUG=797051 TBR=vadimsh@chromium.org Change-Id: I79a77a03b332d7f4bfbe8208928d67194dfc1854 Reviewed-on: https://chromium-review.googlesource.com/897685Reviewed-by: Sergey Berezin <sergeyberezin@chromium.org> Commit-Queue: Sergey Berezin <sergeyberezin@chromium.org>
-
Lei Zhang authored
This is needed for run_presubmit.py to work. BUG=pdfium:971 Change-Id: Ib598fbfd6eab3c0b7628301eb3bd54c548a4885e Reviewed-on: https://chromium-review.googlesource.com/898039Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org>
-
Michael Moss authored
This has been supported in gclient, and used in DEPS, since https://crrev.com/c/687496. R=dpranke@google.com, iannucci@google.com Bug: 570091,807318 Change-Id: I59935625e3bae6010a371ad7bb1413e177a09176 Reviewed-on: https://chromium-review.googlesource.com/896835Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Michael Moss <mmoss@chromium.org>
-
Michael Moss authored
Flattening currently ignores custom_vars, but it looks like that was just an attempt to avoid including all the runtime-calculated values (e.g. the host OS) in the flattened output, and not because there's any real issue with supporting explicit overrides. This is useful for changing default values in the flattened buildspecs (e.g. to enable internal checkouts by default). R=dpranke@google.com, iannucci@google.com Bug: 570091,807318 Change-Id: I6d743f33cf7e3e202d5e68d21657f74f0e4c001b Reviewed-on: https://chromium-review.googlesource.com/895927Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Michael Moss <mmoss@chromium.org>
-
recipe-roller authored
This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (e.g. depot_tools) into downstream projects (e.g. tools/build). More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. recipe_engine: https://crrev.com/d047343541342f1e360ba98704216a717f23a1af [buildbucket] add build_id property (nodir@google.com) TBR=iannucci@chromium.org Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: I0cb3812b1e86d12aaa9dd4101adb40a392b9e99c Reviewed-on: https://chromium-review.googlesource.com/896842Reviewed-by: Recipe Roller <recipe-roller@chromium.org> Commit-Queue: Recipe Roller <recipe-roller@chromium.org>
-
- 31 Jan, 2018 2 commits
-
-
Robert Iannucci authored
R=nodir@chromium.org Bug: 801960,804174 Change-Id: I9f87db6be2d9470384d364591b5d5ff3b5a7b3d9 Reviewed-on: https://chromium-review.googlesource.com/894893Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
-
Edward Lemur authored
This will allow us to show the progress when cloning a new repo when running commands like gclient sync. R=agable@chromium.org Bug: 722686 Change-Id: I268cba343ea4c3c024292c9341d5009aa112b184 Reviewed-on: https://chromium-review.googlesource.com/890524 Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by: Aaron Gable <agable@chromium.org>
-
- 29 Jan, 2018 2 commits
-
-
Benjamin Pastene authored
This is necessary for https://chromium-review.googlesource.com/c/chromium/src/+/882196. Bug: 776987 Change-Id: Iec0a960a7d80f3ddbc0252073e30abc5a243f06c Reviewed-on: https://chromium-review.googlesource.com/882318Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Benjamin Pastene <bpastene@chromium.org>
-
Edward Lemur authored
Add an option to not store stdout when running commands unless it's needed. R=agable@chromium.org Bug: 722686 Change-Id: I402c83767097d53e588ba3e8bca89291712a572f Reviewed-on: https://chromium-review.googlesource.com/888584Reviewed-by: Aaron Gable <agable@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org>
-
- 27 Jan, 2018 2 commits
-
-
Nicolas Boichat authored
Bug: Change-Id: I382ed2fe8544583005e7bfa4479600a90b646ca7 Reviewed-on: https://chromium-review.googlesource.com/888118Reviewed-by: Aaron Gable <agable@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Nicolas Boichat <drinkcat@chromium.org>
-
recipe-roller authored
This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (e.g. depot_tools) into downstream projects (e.g. tools/build). More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. recipe_engine: https://crrev.com/e0a35d1c979628a0c8f5f3cf233ea727c7ee2ef5 Add support for unquote to url recipe module (mknyszek@google.com) TBR=iannucci@chromium.org Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: Id8603a0484747885f2c0bb11c61ca224948391a7 Reviewed-on: https://chromium-review.googlesource.com/889941 Commit-Queue: Recipe Roller <recipe-roller@chromium.org> Reviewed-by: Recipe Roller <recipe-roller@chromium.org>
-
- 26 Jan, 2018 2 commits
-
-
John Budorick authored
Change-Id: I46d3bc00a7d66f8754a3b9a535d5d9817166b777 Reviewed-on: https://chromium-review.googlesource.com/889416Reviewed-by: Aaron Gable <agable@chromium.org> Commit-Queue: John Budorick <jbudorick@chromium.org>
-
Aaron Gable authored
I don't know of any use-case where someone would want to use git-cl-patch to pull a (e.g.) chromium change into their (e.g.) v8 checkout. Bug: 803918 Change-Id: Id53f1cc3ab97e623d0098bb366a573b18b54e91a Reviewed-on: https://chromium-review.googlesource.com/876930Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Aaron Gable <agable@chromium.org>
-
- 25 Jan, 2018 1 commit
-
-
Nodir Turakulov authored
Context: https://bugs.chromium.org/p/chromium/issues/detail?id=800355#c22 Prepare git-cl-try to a new format of builders-map.appspot.com response where each entry contains buckets, as opposed to masters. Bug: 800355 Change-Id: I5a90c6c4860a7e1fca843067c477a272d782cba1 Reviewed-on: https://chromium-review.googlesource.com/885100 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Aaron Gable <agable@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
-
- 23 Jan, 2018 1 commit
-
-
Henrique Ferreiro authored
This fixes the case where a new workdir is created from a repository which was previously created with gclient-new-workdir.py and that repository is later deleted, rendering the symbolic links created by gclient-new-workdir.py invalid. It also fixes support_cow() returning 'True' in that case because 'cp --reflink' does not fail when copying a symlink. Bug: 721585 Change-Id: I84f4d80b8698af0da346be559d46a328ec0d0e9b Reviewed-on: https://chromium-review.googlesource.com/842402Reviewed-by: Aaron Gable <agable@chromium.org> Commit-Queue: Dirk Pranke <dpranke@chromium.org>
-
- 21 Jan, 2018 1 commit
-
-
John Budorick authored
Bug: 789809 Change-Id: I9942eaa613d51edd77ee5195603932a103f5e3cd Reviewed-on: https://chromium-review.googlesource.com/829953 Commit-Queue: John Budorick <jbudorick@chromium.org> Reviewed-by: Aaron Gable <agable@chromium.org>
-
- 18 Jan, 2018 1 commit
-
-
Robert Iannucci authored
In particular this should: * Now ignore `-S`, which breaks all VirtualEnvs * Properly parse the python command line in more cases * No longer ignore PYTHONPATH (essential for launcher scripts in src.git which set PYTHONPATH before invoking python) 38335de5a Roll recipe dependencies (trivial). c20873b37 Roll luci-go (1 commit) 4d90f2197 Roll recipe dependencies (trivial). 79d3339be Roll recipe dependencies (trivial). 9f9a14311 On workflow launched error, log run ID 4c5a25ed7 Roll recipe dependencies (trivial). d7160f243 Roll luci-go (4 commits) ec1a77841 [dockerbuild] Add tlslite. bfbf1dfda Roll infra/luci/ a9cc99df8..ff3140a58 (49 commits) 978202c4c Roll recipe dependencies (trivial). 23b594dff Revert golang.org/x/sys to 52ba35ddf9b65dc3ad27218743aa2444fe13b690 516c58022 [Monorail] Find protoc and plugin at their new locations. 413b8f38d [buildbucket] access: add Makefile 073a90247 Roll recipe dependencies (trivial). 454664529 Add github.com/VividCortex/mysqlerr to Go dependencies 715ed81d4 [som] update relnotes for weekly push b17e9543a [buildbucket] Add buildbucket_template_canary swarming tag. ebb7b62de Roll recipe dependencies (trivial). a1b7ba838 Roll recipe dependencies (trivial). 56ccb3b11 Roll luci-go (2 commits) d3c73486c [Findit] Move UpdateAnalysisResult from swarming_util.py to services/test_failure/test_failure_analysis 4a63f0820 [Monorail] Set up Polymer dev environment in Monorail. 2ee6775c1 Roll recipe dependencies (trivial). 54837b79e Roll recipe dependencies (trivial). 31e8d5ef0 Roll recipe dependencies (trivial). 8c103759a Roll recipe dependencies (trivial). 717f4ac15 Roll recipe dependencies (trivial). 55c3a19eb Roll luci-go (3 commits) 8b6a95944 Set build_exit_status on api.goma.stop. b9384470c Roll recipe dependencies (trivial). 37c8d15de Roll recipe dependencies (trivial). 80475628c Roll recipe dependencies (trivial). 7870bfba3 Roll recipe dependencies (trivial). 0a0d75d59 Roll recipe dependencies (trivial). 37043c2b3 Roll luci-go 8b66950f2 Roll luci-go [9 commits] 99c8a8c40 [Findit] Merge and move logic of getting step log to build_util.py 9183a2f90 [event-pipeine] update docs with new bq package 81b4a9688 Roll recipe dependencies (trivial). 047e4b422 CIPD: Upgrade to Polymer 2.0 48027dc0a Roll recipe dependencies (trivial). b799468f8 Roll recipe dependencies (trivial). 6fa85358e [test-results] Fix single test results chunked rendering f3bc5ff7c [Predator] Monitor Predator-Wrong-CLs and Predator-Wrong-Components bugs daily. af626d23d [vpython] Fix optional debugging -log-level argument. 036cbdaa5 Roll recipe dependencies (trivial). 3504421a7 [Findit] Move swarmbot related logic to a new module. 6a21e50cd Rename AnalyzerProgress to FunctionProgress e9e7b8d57 Roll recipe dependencies (trivial). ec3390c68 Move tricium/analyzers/ to tricium/functions/ ca9010a1b Roll recipe dependencies (trivial). d80df7710 Roll recipe dependencies (trivial). 0e1aabf13 Roll recipe dependencies (trivial). 92f33daa7 Roll recipe dependencies (trivial). 24115742d Roll luci-go [5 commits] 1259b0d5b [bqschemaupdater] remove directory b858620ca Roll recipe dependencies (trivial). fb4916c75 [doc] update Event Pipeline docs 065dd65b0 [Findit] Fix Type error when extract build info. 9642319bc [Monorail] Catch empty JSON search response 39bd53125 [Findit] Remove duplicated function in try_job.py 8bd31a4f1 Download and build Linux tarball 77f25312e [Findit] Flake Analyzer - Fixing reset to clear suspects 739c48078 [Findit] Flake Analyzer - Fix empty confidence a2073847d Roll recipe dependencies (trivial). df4214209 [eventupload] complete move to luci bc0bab29a [luci-migration] add got_revision to build group key fb0c38e34 Roll infra/go/src/go.chromium.org/luci/ 94f59dfc7..067307a03 (1 commit) 06c9e5e1e [bqschemaupdater] remove old test-results schema a3d7ae5cf Roll recipe dependencies (trivial). 1154ed49c Roll recipe dependencies (trivial). bfcdd50d5 [infra/libs/bigquery] add README f0ff49524 Roll recipe dependencies (trivial). 75c72ee4f Roll recipe dependencies (trivial). 27573df51 Roll recipe dependencies (trivial). eacc34857 Roll recipe dependencies (trivial). d3f8862ca Roll recipe dependencies (trivial). fc48386c2 Roll recipe dependencies (trivial). 5948d8de6 Updates dev server config whitelist. 479540994 Roll recipe dependencies (trivial). efa87446b Roll recipe dependencies (trivial). 97cbabb5b [Findit] Fix bug in TestHeuristicResult. 296b77750 Roll recipe dependencies (trivial). f1123e9a7 [Findit] Flake Analyzer - NextCommitPositionPipeline 779c5a4be [Findit] Flake Analzyer - Skip try jobs for chromium.sandbox 5f8211e2d Roll recipe dependencies (trivial). ede641a68 [Findit] Fix a bug in heuristic pipeline for test failures. 926916c58 Roll recipe dependencies (trivial). 015ff2c3c [led] Add -canary flag to get-builder. a1f61935f Roll luci-go DEPS. da6e85b70 Roll recipe dependencies (trivial). 40574c593 [cipd] Allow '.' in package names. af84863d1 Roll recipe dependencies (trivial). 959c58536 Roll recipe dependencies (trivial). a5a8297ab [Monorail] Add Release Notes doc and link. 04cd58a49 [test-results] Replace instead of append divs that already exist. 5d3455659 Start publishing nightly Linux tarballs R=kbr@chromium.org, nodir@chromium.org, vadimsh@chromium.org Bug: 800662 Change-Id: Ie32f291acd725a6cd977c907e465dba660dfb855 Reviewed-on: https://chromium-review.googlesource.com/874154Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
-
- 12 Jan, 2018 2 commits
-
-
Robert Iannucci authored
This should fix the "halts mid-way" symptoms observed on linux. R=agable@chromium.org, hinoka@chromium.org Bug: 782543 Change-Id: Ia5254b7f8e73b5646f2782e36acc52b4772b095e Reviewed-on: https://chromium-review.googlesource.com/865821Reviewed-by: Ryan Tseng <hinoka@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
-
Bruce Dawson authored
The default description in the editor when you invoke "git cl upload" includes recent commit descriptions, some blank lines and comments, and "Bug: ". The upload script properly strips out the comments but was leaving in the "Bug:" line. This leads to CLs with blank Bug: lines, which is sloppy. It also means that if a user changes their mind and closes the upload editor without adding any content... they would still have a CL created. This change removes the "Bug: " line if nothing has been added to it, thus avoiding uploading a change with an empty description, and avoiding having meaningless Bug: lines. Change-Id: I18c2094e5712d31729899c0ebd0a52de97dc4e7f Reviewed-on: https://chromium-review.googlesource.com/861920Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
-
- 11 Jan, 2018 2 commits
-
-
Robert Iannucci authored
This fixes the bug where virtualenvs bootstrapped from vpython virtualenvs would fail to build. R=nodir@chromium.org, tandrii@chromium.org, vadimsh@chromium.org Bug: 784597,800599 Change-Id: Iddcda5fca5f395f031df7a200c688d55ab74ae95 Reviewed-on: https://chromium-review.googlesource.com/860959Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
-
Vadim Shtayura authored
Brings support for '.' in package names. R=iannucci@chromium.org BUG=800618 Change-Id: I36fd31b0576e002da8d58d7e611742c0aa0b0b57 Reviewed-on: https://chromium-review.googlesource.com/861259Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
-
- 10 Jan, 2018 1 commit
-
-
Koji Ishii authored
This patch adds the standard issue option (-i/--issue) to "git cl try" command. This is useful for maintaining FlagExpectations with fyi bots. Runtime-flag features often see new failures, and a good number of tests are flaky. Maintainers can upload a CL and use cron to run try jobs to collect multiple tests results to find new failures and flaky tests. Change-Id: I069593950023ddae814faf3074c33de4c98cb70e Reviewed-on: https://chromium-review.googlesource.com/850792Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org>
-
- 09 Jan, 2018 3 commits
-
-
Mostyn Bramley-Moore authored
Change-Id: I738c566be04a4ba2f699c1cbe2a8d1f43c2c0e93 Reviewed-on: https://chromium-review.googlesource.com/856616Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Mostyn Bramley-Moore <mostynb@vewd.com>
-
recipe-roller authored
This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (e.g. depot_tools) into downstream projects (e.g. tools/build). More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. recipe_engine: https://crrev.com/d76483b254ec53d583dd4e46cf1e2654590823c8 Remove stale go/cmd/kitchen (maruel@chromium.org) TBR=iannucci@chromium.org Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: I9d2bb1f19286c14ff54c9a8f7cde83cf06b5b724 Reviewed-on: https://chromium-review.googlesource.com/857718Reviewed-by: Recipe Roller <recipe-roller@chromium.org> Commit-Queue: Recipe Roller <recipe-roller@chromium.org>
-
Takuto Ikuta authored
This is full version of https://chromium-review.googlesource.com/823544 After the CL landing, we see no performance regression in bot_update step. And regular 95%ile in 1h window improved from more than 300s to less than or around 200s. See tandrii's query in https://bugs.chromium.org/p/chromium/issues/detail?id=749709#c91 for detail. Let me reduce frequency of slow bot_update step more like below. https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/69844 https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/69886 https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/69892 Bug: 749709 Change-Id: I44474aa9ecdd733d68fd13fe8b791820fb80381f Reviewed-on: https://chromium-review.googlesource.com/838766 Commit-Queue: Takuto Ikuta <tikuta@google.com> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
-