This bug is like bug 989533 and the goal is to run mochitest in nested content process. Please note that the current mach option --nested_oop mochitest is based on --e10s (see bug 1038620), so only e10s tests need to run in nested content process, not all tests.
Armen, may I have you help on this? Currently, I have no clue what to do. Please let me what information you need. Thanks.
I have written some instructions that I hope can get you started: https://wiki.mozilla.org/User:Armenzg/Automation_tricks#How_to_add_a_new_job_to_treeherder Is this job of your similar to another command? Could you please paste what the final command looks like? (Not the mach call). For which platforms is this needed for? We should probably enable it on a disposable branch before running it on any of the other trees. We need to be sure that it runs properly as part of automation.
(In reply to Armen Zambrano - Automation & Tools Engineer (:armenzg) from comment #2) > I have written some instructions that I hope can get you started: > https://wiki.mozilla.org/User:Armenzg/ > Automation_tricks#How_to_add_a_new_job_to_treeherder > Thanks. I'll start looking into it. > Is this job of your similar to another command? > Could you please paste what the final command looks like? (Not the mach > call). Sorry that I don't understand what do you mean about the command. I am totally not familiar with the release engineering. Could you please explain more? > For which platforms is this needed for? > I think linux and linux64 should be enough. BTW, I think we only need to run mochitest. > We should probably enable it on a disposable branch before running it on any > of the other trees. > We need to be sure that it runs properly as part of automation. I am not sure do I really need a disposable branch. Should I do this first and then come back to this bug?
Yes, please. If you could file a dependent bug to You should make sure that this job you want runs properly before getting scheduled on treeherder. It is part of treeherder's visibility policy. If a job is not ready then it needs to be scheduled on a disposable branch or try once to be proven to work locally. If you look at any mochitest log  from treeherder you will see a mozharness command like this: /tools/buildbot/bin/python scripts/scripts/desktop_unittest.py --cfg unittests/linux_unittest.py --mochitest-suite plain-chunked --total-chunks 5 --this-chunk 1 --blob-upload-branch mozilla-central --download-symbols ondemand Once that mozharness script gets to the "run-tests" action  you will see the actual call to the mochitest harness . What parameters would need to changed on  to make your job run? NOTE: As a developer you have to slightly modified a mozharness command to run it locally. Here are the instructions: https://wiki.mozilla.org/ReleaseEngineering/Mozharness/How_to_run_tests_as_a_developer#Common_steps In other words, what do you do to do locally to run this job? (I assume your run it through mach) What does the actuall call to the harness look like? According to all this information we could start looking into adding the config changes needed for mozharness.  http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-linux64/1425505001/mozilla-central_ubuntu64_vm_test-mochitest-1-bm68-tests1-linux64-build9.txt.gz  14:41:43 INFO - ##### Running run-tests step.  14:41:43 INFO - Copy/paste: /builds/slave/test/build/venv/bin/python -u /builds/slave/test/build/tests/mochitest/runtests.py --total-chunks 5 --this-chunk 1 --appname=/builds/slave/test/build/application/firefox/firefox --utility-path=tests/bin --extra-profile-file=tests/bin/plugins --symbols-path=https://ftp-ssl.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-linux64/1425505001/firefox-39.0a1.en-US.linux-x86_64.crashreporter-symbols.zip --certificate-path=tests/certs --autorun --close-when-done --console-level=INFO --setpref=webgl.force-enabled=true --quiet --log-raw=/builds/slave/test/build/blobber_upload_dir/plain-chunked_raw.log --use-test-media-devices --chunk-by-dir=4
Kan-Ru, could you please provide a project name for the disposable branch? I am going to file a bug to create a disposable branch with this name. Thanks.
Let's call it the "rhizome" project ;)