880876 - Roll out talos mozharness on Cedar

Status: RESOLVED FIXED

(Release Engineering :: Applications: MozharnessCore, defect)

Comment 1

[Jason Yeo[:jyeo]]

Attachment: add mozharness repo and enable mozharness

This should be all that we need to do to enable mozharness on Cedar right?

Comment 2

[Armen [:armenzg]]

Comment on attachment 759985 [details] [diff] [review]
add mozharness repo and enable mozharness

We shouldn't point to a different mozharness repo.

If you patches are ready to land to the official mozharness repo, it's time to do so.
I believe you can already do so. Please use this format when pushing to the official mozharness repo: "Bug XXXXXX - summary of the bug. r=nickname_of_reviewer"

The changes will only be live when the changes on the default branch will merge to the production branch.

Comment 3

[Jason Yeo[:jyeo]]

Attachment: Enable talos mozharness on Cedar

Once this is enabled, I should be merging the patches from ash-mozharness into build/mozharness right?

Comment 4

[Armen [:armenzg]]

Comment on attachment 760373 [details] [diff] [review]
Enable talos mozharness on Cedar

Review of attachment 760373 [details] [diff] [review]:
-----------------------------------------------------------------

General FYI, you can check what differences your patches produces by outputting the configuration files.

See https://wiki.mozilla.org/ReleaseEngineering:TestingTechniques#config.py_is_executable.21 for more info.

With regards the patch, see the comment below and the conditional r+. Feel free to land.

::: mozilla/project_branches.py
@@ +232,5 @@
>          },
>      },
>      'cedar': {
> +        'mozharness_repo_path': 'build/mozharness',
> +        'mozharness_repo': 'http://hg.mozilla.org/build/mozharness',

No need to add it here; it is a default implicit value.
On Ash, we use something different than the default.

You get r+ on the condition of removing this 2 lines.

Comment 5

[Jason Yeo[:jyeo]]

Attachment: Enable talos mozharness on Cedar

Since I don't have commit access, I shall attach the patch here.

Comment 6

[Armen [:armenzg]]

Would talos on Cedar work if we're pointing to test datazilla credentials?
    1.12 +    "datazilla_urls": ["https://datazilla.mozilla.org/test"],
    1.13 +    "datazilla_authfile": "http://people.mozilla.com/~yshun/slaves.txt",

I think we're fine but I wanted to check with you first.

Comment 7

[Aki Sasaki (not active)]

a) Does it work on ash?
b) I'm not that familiar with datazilla or how talos works with it.  The ateam may be able to clarify.

Comment 8

[Armen [:armenzg]]

(In reply to Aki Sasaki [:aki] from comment #7)
> a) Does it work on ash?
> b) I'm not that familiar with datazilla or how talos works with it.  The
> ateam may be able to clarify.

jyeo, do you mind finding an answer to this? Thanks!

Comment 9

[Armen [:armenzg]]

The day that we enable this across the board. We will need a patch for mozilla-inbound for the newer talos.json format.
Perhaps we can land it in advance.

Comment 10

[Aki Sasaki (not active)]

As long as we don't touch the talos zip portion, we can roll out the rest in advance.

Comment 11

[Jason Yeo[:jyeo]]

Attachment: Add revision string, new talos version and xperf test suite to talos json

Comment 12

[[e-mail] (:bhearsum)]

in production

Comment 13

[Jason Yeo[:jyeo]]

Attachment: use hg instead of hgtool

Comment 14

[Jason Yeo[:jyeo]]

I should have diff'ed the mozharness version of talos.py with ash-mozharness version earlier on. My bad.

Comment 15

[Jonathan Griffin (:jgriffin)]

Comment on attachment 772107 [details] [diff] [review]
use hg instead of hgtool

in production