Extend chromium_tests trigger to work across masters.

Extend chromium_tests trigger to work across masters.

A bot can specify "parent_mastername" to choose which master to trigger from.
Also, merge all the trigger steps to one. For perf bots, it was generating 20+ steps.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=300383

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=300535

[dtu, 2016-04-28 14:31:52]

Description was changed from

==========
Extend chromium_tests trigger to work across masters.

A bot can specify parent_master to determine which master to trigger from.


BUG=
==========

to

==========
Extend chromium_tests trigger to work across masters.

A bot can specify parent_master to choose which master to trigger from.
Also, merge all the trigger steps to one. For some bots, it was generating
upwards of 30 steps.
==========

[dtu, 2016-04-28 14:32:08]

dtu@chromium.org changed reviewers:
+ phajdan.jr@chromium.org

[dtu, 2016-04-28 14:32:24]

Description was changed from

==========
Extend chromium_tests trigger to work across masters.

A bot can specify parent_master to choose which master to trigger from.
Also, merge all the trigger steps to one. For some bots, it was generating
upwards of 30 steps.
==========

to

==========
Extend chromium_tests trigger to work across masters.

A bot can specify "parent_master" to choose which master to trigger from.
Also, merge all the trigger steps to one. For some bots, it was generating
upwards of 30 steps.
==========

[dtu, 2016-04-28 18:08:02]

Description was changed from

==========
Extend chromium_tests trigger to work across masters.

A bot can specify "parent_master" to choose which master to trigger from.
Also, merge all the trigger steps to one. For some bots, it was generating
upwards of 30 steps.
==========

to

==========
Extend chromium_tests trigger to work across masters.

A bot can specify "parent_master" to choose which master to trigger from.
Also, merge all the trigger steps to one. For perf bots, it was generating 20+
steps.
==========

[Paweł Hajdan Jr., 2016-04-29 18:49:26]

LGTM w/comment

https://codereview.chromium.org/1928783004/diff/20001/scripts/slave/recipe_mo...
File scripts/slave/recipe_modules/chromium_tests/bot_config_and_test_db.py
(right):

https://codereview.chromium.org/1928783004/diff/20001/scripts/slave/recipe_mo...
scripts/slave/recipe_modules/chromium_tests/bot_config_and_test_db.py:194:
bot_config.get('parent_master', mastername) == parent_mastername)
Let's be consistent and use 'parent_mastername' (instead of 'parent_master')
here.

[dtu, 2016-04-30 02:49:35]

Description was changed from

==========
Extend chromium_tests trigger to work across masters.

A bot can specify "parent_master" to choose which master to trigger from.
Also, merge all the trigger steps to one. For perf bots, it was generating 20+
steps.
==========

to

==========
Extend chromium_tests trigger to work across masters.

A bot can specify "parent_mastername" to choose which master to trigger from.
Also, merge all the trigger steps to one. For perf bots, it was generating 20+
steps.
==========

[dtu, 2016-04-30 02:51:06]

The CQ bit was checked by dtu@chromium.org

[dtu, 2016-04-30 02:51:07]

https://codereview.chromium.org/1928783004/diff/20001/scripts/slave/recipe_mo...
File scripts/slave/recipe_modules/chromium_tests/bot_config_and_test_db.py
(right):

https://codereview.chromium.org/1928783004/diff/20001/scripts/slave/recipe_mo...
scripts/slave/recipe_modules/chromium_tests/bot_config_and_test_db.py:194:
bot_config.get('parent_master', mastername) == parent_mastername)
On 2016/04/29 at 18:49:26, Paweł Hajdan Jr. wrote:
> Let's be consistent and use 'parent_mastername' (instead of 'parent_master')
here.

Done.

[dtu, 2016-04-30 02:51:08]

The patchset sent to the CQ was uploaded after l-g-t-m from
phajdan.jr@chromium.org
Link to the patchset: https://codereview.chromium.org/1928783004/#ps40001
(title: "parent_master --> parent_mastername")

[commit-bot: I haz the power, 2016-04-30 02:51:16]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1928783004/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1928783004/40001

[commit-bot: I haz the power, 2016-04-30 02:56:32]

Description was changed from

==========
Extend chromium_tests trigger to work across masters.

A bot can specify "parent_mastername" to choose which master to trigger from.
Also, merge all the trigger steps to one. For perf bots, it was generating 20+
steps.
==========

to

==========
Extend chromium_tests trigger to work across masters.

A bot can specify "parent_mastername" to choose which master to trigger from.
Also, merge all the trigger steps to one. For perf bots, it was generating 20+
steps.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=300383
==========

[commit-bot: I haz the power, 2016-04-30 02:56:33]

Committed patchset #3 (id:40001) as
http://src.chromium.org/viewvc/chrome?view=rev&revision=300383

[Dirk Pranke, 2016-04-30 18:10:18]

A revert of this CL (patchset #3 id:40001) has been created in
https://codereview.chromium.org/1932213004/ by dpranke@chromium.org.

The reason for reverting is: I strongly suspect this severely broke build
triggering:

https://build.chromium.org/p/chromium.linux/builders/Linux%20Builder/builds/6...

crbug.com/608167.

[dtu, 2016-05-04 00:35:59]

Description was changed from

==========
Extend chromium_tests trigger to work across masters.

A bot can specify "parent_mastername" to choose which master to trigger from.
Also, merge all the trigger steps to one. For perf bots, it was generating 20+
steps.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=300383
==========

to

==========
Extend chromium_tests trigger to work across masters.

A bot can specify "parent_mastername" to choose which master to trigger from.
Also, merge all the trigger steps to one. For perf bots, it was generating 20+
steps.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=300383
==========

[dtu, 2016-05-04 00:40:36]

Fixed! PTAL.
Let me know if you prefer a separate CL or CLs for the reland.

https://codereview.chromium.org/1928783004/diff/80001/scripts/slave/recipes/c...
File
scripts/slave/recipes/chromium.expected/full_chromium_perf_Win_x64_Builder.json
(right):

https://codereview.chromium.org/1928783004/diff/80001/scripts/slave/recipes/c...
scripts/slave/recipes/chromium.expected/full_chromium_perf_Win_x64_Builder.json:876:
{
This is the new cross-master trigger.

https://codereview.chromium.org/1928783004/diff/80001/scripts/slave/recipes/c...
File
scripts/slave/recipes/chromium.expected/full_chromium_perf_fyi_Win_x64_FYI_Builder.json
(left):

https://codereview.chromium.org/1928783004/diff/80001/scripts/slave/recipes/c...
scripts/slave/recipes/chromium.expected/full_chromium_perf_fyi_Win_x64_FYI_Builder.json:186:
{
Note the removal of the old trigger.

[nodir, 2016-05-04 01:41:46]

nodir@chromium.org changed reviewers:
+ nodir@chromium.org

[nodir, 2016-05-04 01:41:47]

no need to specify bucket if you are intend to trigger a build on the same
master

[nodir, 2016-05-04 01:50:34]

err nvm

[dtu, 2016-05-05 23:34:30]

Friendly pong

[nodir, 2016-05-06 00:58:30]

the part the caused the outage last time lgtm because most of trigger specs do
not have "bucket" parameter anymore, and the one that has (master.chromium.perf)
has ActiveMaster properly passed
(https://code.google.com/p/chromium/codesearch#chromium/build/masters/master.c...)

[dtu, 2016-05-10 22:04:52]

The CQ bit was checked by dtu@chromium.org

[dtu, 2016-05-10 22:04:52]

The patchset sent to the CQ was uploaded after l-g-t-m from
phajdan.jr@chromium.org
Link to the patchset: https://codereview.chromium.org/1928783004/#ps80001
(title: "Include all the master data in the bot db. Change chromium.perf.fyi
builder for coverage.")

[commit-bot: I haz the power, 2016-05-10 22:05:03]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1928783004/80001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1928783004/80001

[commit-bot: I haz the power, 2016-05-10 22:06:37]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-05-10 22:06:39]

Try jobs failed on following builders:
  Build Try Recipe Test Trusty64 on tryserver.infra (JOB_FAILED,
https://build.chromium.org/p/tryserver.infra/builders/Build%20Try%20Recipe%20...)

[dtu, 2016-05-10 22:13:09]

The CQ bit was checked by dtu@chromium.org

[dtu, 2016-05-10 22:13:09]

The patchset sent to the CQ was uploaded after l-g-t-m from nodir@chromium.org,
phajdan.jr@chromium.org
Link to the patchset: https://codereview.chromium.org/1928783004/#ps100001
(title: "REbase")

[commit-bot: I haz the power, 2016-05-10 22:13:16]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1928783004/100001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1928783004/100001

[commit-bot: I haz the power, 2016-05-10 22:18:34]

Description was changed from

==========
Extend chromium_tests trigger to work across masters.

A bot can specify "parent_mastername" to choose which master to trigger from.
Also, merge all the trigger steps to one. For perf bots, it was generating 20+
steps.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=300383
==========

to

==========
Extend chromium_tests trigger to work across masters.

A bot can specify "parent_mastername" to choose which master to trigger from.
Also, merge all the trigger steps to one. For perf bots, it was generating 20+
steps.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=300383

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=300535
==========

[commit-bot: I haz the power, 2016-05-10 22:18:35]

Committed patchset #6 (id:100001) as
http://src.chromium.org/viewvc/chrome?view=rev&revision=300535