Hi All,
I’d like to test mulet on linux but the mulet wiki send me here: Taskcluster linux mulet
From here i don’t really get if/where i can get the linux version of mulet…
One of the option was to build it locally following the script here : Task inspector taskcluster mulet
But I feel i require a lot of source download and i have limited space on my laptop…
Anyone could give me some hints on how i can have this done ?
Thanks !
Matth
Wiki is out of date. Take the latest green mulet build on pine.
Hi All,
I’d like to test mulet on linux but the mulet wiki send me here:
Taskcluster linux muletFrom here i don’t really get if/where i can get the linux version of
mulet…One of the option was to build it locally following the script here :
Task inspector taskcluster muletBut I feel i require a lot of source download and i have limited space on
my laptop…
Look on https://treeherder.mozilla.org/#/jobs?repo=pine&filter-tier=1&filter-tier=2&filter-tier=3 for “Mulet linux” lines, click on the green “+3”, a “B” will appear, click on it, a panel will appear at the bottom, with a link “Inspect task”, click it. In the page that will open, you have a list of artifacts, download “target.tar.bz2”
Thanks lissyx !
I manage to get a build but strangle when i startup mulet with the gaia profile it stay stuck on a black screen:
output from the console when i startup mulet
Thanks for the help
Matth
How did you built you gaia profile? Where does it comes from?
Here is what is have done:
git clone https://github.com/mozilla-b2g/gaia.git
wget mulet from treeherder (tried version 50.0a1 and 49.0a1)
cd gaia && make
When i run mulet i have only a black screen.
then i have tried,
git reset --hard origin/kanikani
make
When i run mulet i have only a black screen as well.
how do you run mulet?
by running this command:
firefox-bin --no-remote --profile ~/gaia/profile
Did you ever get past the black screen? I’m getting something similar when using
make mulet
from inside gaia (on both master and kanikani branches). The build appears to work and I can run it either by building a debug profile
DEBUG=1 DESKTOP=0 make
firefox-bin --no-remote --profile ~/gaia/profile-debug
or a non-debug profile
make
firefox-bin --no-remote --profile ~/gaia/profile
but in all cases mulet starts but I end up with a black screen.
I tried with “compiled version” of Mulet from taskcluster , I had black screen , but in fact, that what a “bad” version of Mulet .
Last time tried with https://queue.taskcluster.net/v1/task/Tg4Sld58RwmUbJnVPwBXvg/runs/0/artifacts/public%2Fbuild%2Ftarget.tar.bz2 wich is in the iteration https://tools.taskcluster.net/task-inspector/#Tg4Sld58RwmUbJnVPwBXvg/0
I don’t know if it’s the best build, but it works for me.
I’m using the compiled version from task cluster as well, and for me it only boots up when I use gaia/profile and not gaia/profile-debug. In the latter case, I get a Firefox browser chrome with no URL in the address base, and just white in the main area. If I try to manually go to chrome://b2g/content/shell.html I get a plain black page, nothing else.
The other problem I’m having is that I’m not able to use the Test Agent once Mulet is running. It always says “One or more files are unavailable …” even though I am supposedly running test-agent-server as per the README. Is anyone else able to use the test agent at the moment?
There is a bug filed already for the profile debug issue. And i have no
idea for test agent but it is not surprising that it is broken.
I’m using the compiled version from task cluster as well, and for me it
only boots up when I use gaia/profile and not gaia/profile-debug. In the
latter case, I get a Firefox browser chrome with no URL in the address
base, and just white in the main area. If I try to manually go to
chrome://b2g/content/shell.html I get a plain black page, nothing else.The other problem I’m having is that I’m not able to use the Test Agent
once Mulet is running. It always says “One or more files are unavailable
…” even though I am supposedly running test-agent-server as per the
README. Is anyone else able to use the test agent at the moment?
Visit Topic or reply to this email to respond.
In Reply To
<
https://ci3.googleusercontent.com/proxy/XvlrWBztHJdZa4NRTcnNQqvWtwF8SYlGtxXn4HN1OFTJSC_sOi1jebQf5gbYTzYIBuqN24pdNrpeXb5_mc16MLUherRAKRgH9yajh1MJghyGo-Yihk9VA9N_g8vR5xJPjUZdDl5Az-xxn_0OxajrGGHrg0diAy6HiEb01s-y=s0-d-e1-ft#https://discourse.mozilla-community.org/user_avatar/discourse.mozilla-community.org/sizvix/45/4119_1.png>
sizvix simon g
July 28
I tried with “compiled version” of Mulet from taskcluster , I had black
screen , but in fact, that what a “bad” version of Mulet . Last time tried
with
https://queue.taskcluster.net/v1/task/Tg4Sld58RwmUbJnVPwBXvg/runs/0/artifacts/public%2Fbuild%2Ftarget.tar.bz2
wich is in the iteration https://tools…
This is the bug for DEBUG=1 profiles: https://bugzilla.mozilla.org/show_bug.cgi?id=1265062
Nobody worked on fixing test execution, so it’s expected it is badly broken, but any contribution is welcome!
Ok, I’ll start a new topic for the test runner under Coding.
PS. if anyone is using Arch Linux, I’ve made an AUR package for installing the latest build of Mulet from TaskCluster here: https://aur.archlinux.org/packages/mulet-nightly-bin.
@lissyx, do you know if there’s some way to get dev tools in Mulet, or is it only possible to debug using the browser console?
Devtools were working in mulet just open them
@lissyx, do you know if there’s some way to get dev tools in Mulet, or is
it only possible to debug using the browser console?
Here’s a screenshot of what I see in Mulet. No change if I go to Tools > Web Developer > Toggle Tools. Is something not switched on in the taskcluster builds, perhaps, or is it my system somehow? I’m starting it using path/to/mulet/firefox --no-remote --profile ./profile from gaia dir.
I guess the best explanation is that devtools in Mulet are broken and
someone is going to have to investigate to fix this :-/
Here’s a screenshot of what I see in Mulet. No change if I go to Tools >
Web Developer > Toggle Tools. Is something not switched on in the
taskcluster builds, perhaps, or is it my system somehow? I’m starting it
using path/to/mulet/firefox --no-remote --profile ./profile from gaia dir.
I have to use the option " --devtools " to activate the devtools :
/home/sizvix/B2GOS/mulet_0722/firefox-bin --no-remote --profile /home/sizvix/B2GOS/gaia/profile --devtools
Thanks! This works for me as well!
