Closed Bug 1110682 Opened 5 years ago Closed 2 years ago

[Travis] Run tests on v2.0m branch

Categories

(Firefox OS Graveyard :: Gaia::Build, defect)

x86_64
Linux
defect
Not set

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: seinlin, Unassigned)

Details

Attachments

(1 file)

No description provided.
Julien, To run gaia test on v2.0m, do we need to modify the branch in .travis.yml
? As I know, now gaia test is running on treeherder, but I now sure if this is still valid.
Attachment #8535536 - Flags: feedback?(felash)
Hey Kevin, can you possibly help here?
Flags: needinfo?(kgrandon)
Yes, the changes here would be necessary to run travis on v2.0m - though I didn't think we were running travis any more.
Flags: needinfo?(kgrandon)
Kevin, the underlying question is: why don't the tests for v2.0m run on treeherder ? :)
Flags: needinfo?(kgrandon)
I think the reason we don't have tests running is because we're doing a poor job communicating these branches out to the larger team - I don't even know why we have most of these release branches are for in the first place, or when they get created.

You're probably missing some step where rel-eng or sheriffs create the necessary mozilla-b2g32_v?? integration for you. Unfortunately I don't really know what that step is.
Flags: needinfo?(kgrandon)
Ed/Bhavana - could you help us track down what we need to do or who we need to talk to have testing running on v2.0m? Do we need to create a mozilla-b2g32_v2.0m branch?
Flags: needinfo?(emorley)
Flags: needinfo?(bbajaj)
(In reply to Kevin Grandon :kgrandon from comment #6)
> Ed/Bhavana - could you help us track down what we need to do or who we need
> to talk to have testing running on v2.0m? Do we need to create a
> mozilla-b2g32_v2.0m branch?

I'd ask #releng or release@moco, this is more release engineering's domain :-)
(I'm also no longer on the sheriff team)

Do give me a shout if you struggle to get answers from them though & I'll chase it up for you.
Flags: needinfo?(emorley)
> I don't even know why we have most of these release branches are for in the first place, or when they get created.

The answer is quite simple: they're device-specific :)
Comment on attachment 8535536 [details] [diff] [review]
run-gaia-test.diff

you can land this on the v2.0m branch but I think we really need to have v2.0m running on treeherder.
Attachment #8535536 - Flags: feedback?(felash) → feedback+
Comment on attachment 8535536 [details] [diff] [review]
run-gaia-test.diff

Julien, Thanks! Could you also review this patch? We'll land this patch and also try to find out why treeherder is not running on v2.0m.
Attachment #8535536 - Flags: review?(felash)
Comment on attachment 8535536 [details] [diff] [review]
run-gaia-test.diff

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

r=me to land on the v2.0m branch
Attachment #8535536 - Flags: review?(felash) → review+
(In reply to Kevin Grandon :kgrandon from comment #6)
> Ed/Bhavana - could you help us track down what we need to do or who we need
> to talk to have testing running on v2.0m? Do we need to create a
> mozilla-b2g32_v2.0m branch?

That was already flagged to have automation running to the devices team when they wanted to create the device branches but they were still created without tests! They need to work closely with releng to get the set-up as needed.
Flags: needinfo?(bbajaj)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.