Closed Bug 1136683 Opened 9 years ago Closed 9 years ago

[Meta] Fix Integration tests in v2.2 branch

Categories

(Firefox OS Graveyard :: Gaia, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: apastor, Unassigned)

References

Details

Currently, v2.2 branch is red in gaia-try. This meta bug is for keeping track of the remaining work for making it green again

https://treeherder.mozilla.org/#/jobs?repo=gaia-try&revision=a600d2bcc978
Depends on: 1136698
Depends on: 1121274
Depends on: 1129541
Depends on: 1136755
Depends on: 1137277
Green again:

https://treeherder.mozilla.org/#/jobs?repo=gaia-try&revision=04f1e2bdf8ed
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Seems it's getting red again: https://treeherder.mozilla.org/#/jobs?repo=gaia-try&revision=e3b91c3a2525
Could gij unhidden on mozilla-b2g37_v2_2 to have sheriff taking care of that?

Kevin, I was following previous discussion on dev-gaia[1, 2], you mentioned we could uplift the harness changes that Gareth made, does that means uplift bug 1127975 to 2.2 and we can unhidden gij on mozilla-b2g37_v2_2? 

[1]: https://groups.google.com/forum/#!topic/mozilla.dev.gaia/uRcI-9rJIxI/discussion
[2]: https://groups.google.com/forum/#!topic/mozilla.dev.gaia/pxdLzYKTGaA/discussion
Flags: needinfo?(kgrandon)
Flags: needinfo?(apastor)
Yes, let's uplift bug 1127975 to 2.2. That should make things better. I'll submit a pull request to do so now.

We can't unhide it until we're fully green. Alberto's been doing most of the work there, but I'll see if I can pitch in.
Flags: needinfo?(kgrandon)
Flags: needinfo?(apastor)
See Also: → 1142377
Still some issues

https://treeherder.mozilla.org/#/jobs?repo=gaia-try&revision=c5365b9f2476
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 1142439
Depends on: 1142558
Seems pretty stable now 

https://treeherder.mozilla.org/#/jobs?repo=gaia-try&revision=d57ff048ca30
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.