1271394 - Enable all standard tests on projects/larch branch.

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task)

Description

[Kannan Vijayan [:djvj]]

We need all the standard tests that run on mozilla-inbound to be enabled on projects/larch.

Comment 1

[Kim Moir [:kmoir] ET]

aselegea: I think this just means the same builds/tests as on mozilla-inbound

Comment 2

[Kannan Vijayan [:djvj]]

aselegea: what kmoir said is correct.  We'd like the same set of tests enabled on projects/larch as are enabled on mozilla-inbound.

Sorry if my initial wording was not very clear.

Comment 3

[Alin Selagea [:aselagea]]

Thanks, will start working on enabling the tests on larch.

Comment 4

[Alin Selagea [:aselagea]]

Attachment: bug_1271394.patch

Attaching the patch to enable the same tests on larch as on m-i.

Comment 5

[Alin Selagea [:aselagea]]

Attachment: larch-tests.txt

Comment 6

[Alin Selagea [:aselagea]]

Attachment: mozilla-inbound-tests.txt

Comment 7

[Kim Moir [:kmoir] ET]

Looking at larch on treeherder, there don't seem to be any builds enabled.  Do they need to be enabled?

Comment 8

[Alin Selagea [:aselagea]]

Attachment: builders.txt

Oh, it seems the builders from the patch attached are also added. 
@Kannan: please let me know if they are also needed. Otherwise, I'll rework the patch to remove them.

Comment 9

[Kannan Vijayan [:djvj]]

We do need the builds on treeherder.  I just checked and they don't seem to be enabled.  I'm not sure what you mean in the comment above.

The builders from which patch are added to where?  We need CI builds on every checkin on projects/larch, just like on m-i and m-c.

Comment 10

[Alin Selagea [:aselagea]]

(In reply to Kannan Vijayan [:djvj] from comment #9)
> We do need the builds on treeherder.  I just checked and they don't seem to
> be enabled.  I'm not sure what you mean in the comment above.
> 
> The builders from which patch are added to where?  We need CI builds on
> every checkin on projects/larch, just like on m-i and m-c.

Sorry for the confusion. 
What I meant to say is that the changes from'bug_1271394.patch' will also enable the builders listed in 'builders.txt' attachment (besides enabling the tests that you can see on 'larch-tests.txt').

The bug title only mentions 'tests' that we want to enable, so I guess Kim wanted to know if builders are also required: https://bugzilla.mozilla.org/show_bug.cgi?id=1271394#c7.

That being said, if we want the same builds and tests on larch as on mozilla-inbound, then I think the patch is ok for review :-)

Comment 11

[Kim Moir [:kmoir] ET]

Comment on attachment 8752216 [details] [diff] [review]
bug_1271394.patch

You need the builds enabled to trigger the tests and have binaries to run tests against.

Noticed that it appears we are running Linux64 builds on buildbot, shouldn't these be on taskcluster since they are turned off on buildbot in bug 1268542

Comment 12

[Alin Selagea [:aselagea]]

Not sure about it, but in bug 1268542 we only disable the builders and tests for Linux64 debug. In 'builders.txt' attachment, I can see 'Linux x86-64 larch debug asan build' (which I'd say is for linux64-asan) and 'Linux x86-64 larch debug static analysis build' (which I don't seem to find where it belongs to).

Am I missing something here?

Comment 13

[Kim Moir [:kmoir] ET]

I think you will need to add something here
http://hg.mozilla.org/integration/mozilla-inbound/file/tip/testing/taskcluster/tasks/branches

so that builders that are disabled on buildbot will run on taskcluster and are enabled on larch just as they are for m-i

Comment 14

[Alin Selagea [:aselagea]]

Attachment: [TC]bug_1271394.patch

We'd like to run the same TC jobs on larch as on m-i. Adding a new folder for larch and the 'job_flags.yml' file for specific builds/tests (the same as with m-i).

Comment 15

[Wander Lairson Costa]

Comment on attachment 8754322 [details] [diff] [review]
[TC]bug_1271394.patch

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

Notice you have to add it to mozilla-taskcluster as well.

Comment 16

[Release Engineering SlaveAPI Service]

In production: https://hg.mozilla.org/build/buildbot-configs/rev/151b97c26b65

Comment 17

[Kannan Vijayan [:djvj]]

Whee!! Thank you.  I can see our first test build running.

I don't see MacOS or Android tests running.. are those not enabled?

Comment 18

[Kannan Vijayan [:djvj]]

I'm seeing the following build error in the logs for windows (and a few other architecures):

CalledProcessError: Command '['hg', 'unbundle', '--traceback', 'https://ftp-ssl.mozilla.org/pub/mozilla.org/firefox/bundles/larch.hg']' returned non-zero exit status 255

Link to example job:
https://treeherder.mozilla.org/#/jobs?repo=larch&selectedJob=470

Is this a repos issue or a build automation issue?

Comment 19

[Kannan Vijayan [:djvj]]

Forgot to needinfo you on last comment.  Please see Comment 18.

Comment 20

[Kannan Vijayan [:djvj]]

Nevermind, found the problem.  It was my issue in code.

Comment 21

[Pulsebot]

https://hg.mozilla.org/integration/mozilla-inbound/rev/7f6080fa6fc3

Comment 22

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/7f6080fa6fc3