On 2019/08/30 23:21, Botond Ballo wrote:
On Fri, Aug 30, 2019 at 6:37 AM ishikawa <ishik...@yk.rim.or.jp> wrote:
I see a couple of submissions in treeherder where I do not
see explicit passing of TryChooser string. Hmm...
https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=c4f1d2a2e2acb8c2acaf6996fdc9947613b4a9c1
https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=df8844eb9048ebd2e3e28a27f1deb39062d5fb7d
Aha, these are only meant for documentation change and no passing of
trychooser string is necessary? But then why the shippable opt build is
performed is beyond me.
The tip commits of those pushes contain a file called
"try_task_config.json" which lists the jobs that will be run. This
file is produced by "mach try fuzzy" (possibly among other things).
Cheers,
Botond
I see. I only scan the first file and did not realize this.
I wish |mach try ...| can be used for C-C without much issue in the future.
TIA
Chiaki
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
