New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 814324 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Feature



Sign in to add a comment

Move results_merger.py to src/testing/scripts

Project Member Reported by eyaich@chromium.org, Feb 21 2018

Issue description

For the perf use case we have forked 

https://cs.chromium.org/chromium/build/scripts/slave/recipe_modules/swarming/resources/results_merger.py

We plan to move this code to 
https://cs.chromium.org/chromium/src/testing/buildbot/scripts/

So that it can be utilized from both src side and build directories so we don't need to have two copies of merging a common format.

 
How do you envision the standard_isolated_script_merge.py invoking the merger script from src? What happens if it can't find it, or if it isn't provided?

Comment 3 by eyaich@chromium.org, Feb 21 2018

Why can't we just call a subprocess to a standard location on src side?
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Sign in to add a comment