New issue
Advanced search Search tips

Issue 655785 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Oct 2016
Cc:
nedngu...@google.com
chrome-trooper-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

Upload to test-results broken on all bots

Project Member Reported by jam@chromium.org, Oct 13 2016 
I see on a bunch of trybots and buildbots this is broken, i.e.

https://build.chromium.org/p/chromium.fyi/builders/Browser%20Side%20Navigation%20Linux/builds/22520
https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_ng/builds/311276

the errors are
Usage: upload_test_results.py [options]

upload_test_results.py: error: no such option: --input-json
step returned non-zero exit code: 2
@@@STEP_WARNINGS@@@

Comment 1 by iannu...@google.com, Oct 14 2016

Cc: nedngu...@google.com
Status: Available (was: Untriaged)
Looks like this was caused by:

$ cd build.git && git log --grep '--input-json'
commit e1068b5b44eace8d671ac9b8147dc95dbb77e11c
Author: recipe-roller <recipe-roller@chromium.org>
Date:   Thu Oct 13 04:28:17 2016 -0700

    Roll recipe dependencies (trivial).

    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
    (or complain)

    build:
      https://crrev.com/1a9df62478f43484695e00ed6a808673461c5736 Rename --input-gtest-json flag to --input-json flag (nednguyen@google.com)

    TBR=martiniss@chromium.org,phajdan.jr@chromium.org
    BUG= 649762 , 655520 

    Recipe-Tryjob-Bypass-Reason: Autoroller
    Bugdroid-Send-Email: False
    Review-Url: https://codereview.chromium.org/2415923002

Comment 2 by iannu...@google.com, Oct 14 2016 

Hm... or maybe it was supposed to have been FIXED by that commit?

Comment 3 by iannu...@google.com, Oct 14 2016

Status: Fixed (was: Available)
Yes, indeed, that commit fixed the issue already.
►

Sign in to add a comment