Closed
Bug 878122
Opened 13 years ago
Closed 13 years ago
Please create Nightly B2G Unagi engineering build against mozilla-central
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: zcampbell, Assigned: mozilla)
References
Details
Attachments
(2 files, 2 obsolete files)
|
2.22 KB,
patch
|
rail
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
|
3.69 KB,
patch
|
Details | Diff | Splinter Review |
For ui-test automation can you create a Nightly engineering build against mozilla-central
Please include a generic zip file name and in a `latest/` directory.
Basically we need the same as this build but with the Engineering flag:
https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-central-unagi/latest/
| Assignee | ||
Updated•13 years ago
|
Assignee: nobody → aki
| Assignee | ||
Comment 1•13 years ago
|
||
Attachment #756664 -
Flags: review?(rail)
Comment 2•13 years ago
|
||
Comment on attachment 756664 [details] [diff] [review]
unagi-eng on m-c
lgtm
Attachment #756664 -
Flags: review?(rail) → review+
| Assignee | ||
Comment 3•13 years ago
|
||
Comment on attachment 756664 [details] [diff] [review]
unagi-eng on m-c
https://hg.mozilla.org/build/buildbot-configs/rev/7ce252a672fa
Attachment #756664 -
Flags: checked-in+
| Reporter | ||
Comment 4•13 years ago
|
||
That was quick, thanks!
Comment 5•13 years ago
|
||
in production
| Reporter | ||
Comment 6•13 years ago
|
||
I can't find it; where are you hiding it?
Comment 7•13 years ago
|
||
I see two pending 'b2g_mozilla-central_unagi_eng_nightly' jobs on
https://tbpl.mozilla.org/?showall=1&jobname=eng
but not any builders on the buildbot masters to carry those out.
| Assignee | ||
Comment 8•13 years ago
|
||
Looks like a 2nd reconfig has gotten these running.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 9•13 years ago
|
||
https://tbpl.mozilla.org/php/getParsedLog.php?id=23728943&tree=Mozilla-Central#error1
Not sure why we're trying to use mozdevice here?
Status: RESOLVED → REOPENED
Flags: needinfo?
Resolution: FIXED → ---
| Assignee | ||
Comment 10•13 years ago
|
||
I think this is dying when trying to create the flash zip for unagi-eng on m-c.
Marshall: is the appropriate code checked into m-c for this?
Flags: needinfo?
| Assignee | ||
Updated•13 years ago
|
Flags: needinfo?(marshall)
| Assignee | ||
Comment 11•13 years ago
|
||
[15:01] <jgriffin> it looks like there's a script which is used for staging updates that uses a part of Marionette
[15:02] <jgriffin> aki: I think the in-tree version of Marionette in mozilla-b2g doesn't have that dependency
[15:02] <aki> jgriffin: ok. that would make sense since we're building unagi-eng on b2g18* but not m-c yet
[15:03] <aki> jgriffin: what should i do? ask for that dependency to be removed, or add a mozdevice/marionette virtualenv to the build, or ?
[15:03] <jgriffin> the latter, if possible
[15:05] <aki> jgriffin: should build.sh handle that, or do we need that logic in mozharness
[15:05] <jgriffin> I don't know anything about build.sh, but theoretically it should be easy to get mozharness to do this
[15:06] <aki> yeah, i need to know where to find those bits, what modules are required, and then call the flashing target with the appropriate python
[15:06] <aki> and hopefully it would work across all branches, so i don't have to special case m-c
[15:07] <jgriffin> I think the same logic should work across trees
[15:08] <jgriffin> basically it needs testing/marionette/client, and the mozbase packages (from testing/mozbase) that are in setup.py tehre
Flags: needinfo?(marshall)
| Assignee | ||
Comment 12•13 years ago
|
||
Comment 11 is complicated by the fact that we will have to create the virtualenv inside mock.
| Assignee | ||
Comment 13•13 years ago
|
||
We don't currently have setup_development.py support in mozharness, but I can point to each mozbase module individually.
| Assignee | ||
Comment 14•13 years ago
|
||
(In reply to Aki Sasaki [:aki] from comment #13)
> We don't currently have setup_development.py support in mozharness, but I
> can point to each mozbase module individually.
(v)deathduck:/src/unagi-eng-mc [16:34:58]
610$ pip install /src/clean/mozilla-central/testing/mozbase
("Directory %r is not installable. File 'setup.py' not found.", '/src/clean/mozilla-central/testing/mozbase')
Storing complete log in /Users/asasaki/.pip/pip.log
Moving setup_development.py to setup.py could fix this. Proceeding with a verbose listing of mozbase modules for now.
| Assignee | ||
Comment 15•13 years ago
|
||
It seems more likely I'm going to break something than fix this bug + not affect any other branches, so I'm going to do some testing first.
Comment 16•13 years ago
|
||
Hidden on tbpl so we don't have to stare at its glaring red face.
| Assignee | ||
Comment 17•13 years ago
|
||
Looks like we're creating the virtualenv now, but it's not in mock.
I noticed we're creating a ./_virtualenv/bin/python in mock through build.sh; I'm trying to use that now.
| Assignee | ||
Comment 18•13 years ago
|
||
... and this won't work on b2g18 anyway, since moznetwork doesn't exist there:
http://hg.mozilla.org/releases/mozilla-b2g18/file/997cdbf5d012/testing/mozbase
Could we remove the dependency for marionette/mozdevice in m-c, please?
| Assignee | ||
Comment 20•13 years ago
|
||
Completely bypasses mozharness.base.python.VirtualenvMixin.create_virtualenv(), since we're in a mock environment and have to deal with setup_development.py which doesn't behave with pip.
Attachment #757708 -
Attachment is obsolete: true
Comment 21•13 years ago
|
||
(In reply to Aki Sasaki [:aki] from comment #18)
> ... and this won't work on b2g18 anyway, since moznetwork doesn't exist
> there:
> http://hg.mozilla.org/releases/mozilla-b2g18/file/997cdbf5d012/testing/
> mozbase
>
> Could we remove the dependency for marionette/mozdevice in m-c, please?
I'd be more inclined to land moznetwork in mozilla-b2g18; would that be a viable alternative?
Flags: needinfo?(jgriffin)
| Assignee | ||
Comment 22•13 years ago
|
||
Let me test my latest patch; if that works we may not need to.
Fingers crossed.
Comment 23•13 years ago
|
||
Or do you mean, remove the marionette dependency from stage-update.py?
| Assignee | ||
Comment 24•13 years ago
|
||
(In reply to Jonathan Griffin (:jgriffin) from comment #23)
> Or do you mean, remove the marionette dependency from stage-update.py?
If that happened, unagi-eng nightlies on m-c would Just Work without additional b2g_build.py changes, so yes, that would be nice.
I'm not sure what that dependency is giving us, however, so I can't say whether we need it.
Comment 25•13 years ago
|
||
It's not giving us much, tbh, I can make a hack to remove it.
| Assignee | ||
Comment 26•13 years ago
|
||
Cool. dev-master01 just died, so I still don't know if my latest update to attachment 758039 [details] [diff] [review] helps or not.
| Assignee | ||
Comment 27•13 years ago
|
||
If we still want to create a mozbase virtualenv inside mock, this patch will do it. I think we're good once m-i merges into m-c, though.
Attachment #758039 -
Attachment is obsolete: true
| Assignee | ||
Comment 28•13 years ago
|
||
(Testing that patch against m-b2g18 just in case.)
| Assignee | ||
Comment 29•13 years ago
|
||
(In reply to Aki Sasaki [:aki] from comment #28)
> (Testing that patch against m-b2g18 just in case.)
This went green in staging.
Jonathan's patch merged to m-c; re-kicked the unagi-eng m-c nightly.
| Assignee | ||
Comment 30•13 years ago
|
||
https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-central-unagi-eng/latest/
https://tbpl.mozilla.org/php/getParsedLog.php?id=23831038&tree=Mozilla-Central&full=1
\o/
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 31•13 years ago
|
||
Thanks Aki, so this is ready for human consumption?
I've flashed it and it's alive but I just want to know whether it's OK for me to start raising bugs.
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•