1183155 - Mozharness still needs a buildprops.json file

Status: RESOLVED INVALID

(Release Engineering :: Applications: MozharnessCore, defect)

Description

[Kartikaya Gupta (email:[e-mail])]

Attachment: Output from command run

I got a loaner (bug 1182839) and followed the steps at https://wiki.mozilla.org/ReleaseEngineering/Mozharness/How_to_run_tests_as_a_developer to run a b2g emulator mochitest chunk. This is the command I ran:

python scripts/scripts/b2g_emulator_unittest.py --cfg b2g/emulator_automation_config.py --test-suite mochitest --this-chunk 8 --total-chunks 9 --blob-upload-branch try --download-symbols ondemand --installer-url http://pvtbuilds.pvt.build.mozilla.org/pub/mozilla.org/b2g/try-builds/[e-mail]-f91134f3e97a/try-emulator/emulator.tar.gz --test-url http://pvtbuilds.pvt.build.mozilla.org/pub/mozilla.org/b2g/try-builds/[e-mail]-0658841534fa/try-emulator/b2g-42.0a1.en-US.android-arm.common.tests.zip 2>&1 | tee run.log

And attached is the output it gave me, indicating that it still needed a buildprops.json file. Looking further down in the wiki page into the deprecated steps section I found some info on how to make such a buildprops.json file and following those steps seemed to get past that error. However it still seems like a bug that we need to create a buildprops.json file, from my reading of the wiki page.

Comment 1

[Jordan Lund (:jlund)]

buildprops.json in automation is dynamic (downloaded new for each build/test job run in buildbot). it contains the test url and installer url. but since you are running this locally on a loaned machine, you can specify things like the installer url explicitly. Which looks like you are but you also need to tell mozharness to not look for buildprops.json. You do that by running with: --no-read-buildbot-config

buried in the above wiki you mentioned says to pass --no-read-buildbot-config if this is a loaned machine: https://wiki.mozilla.org/ReleaseEngineering/Mozharness/How_to_run_tests_as_a_developer#...on_a_loaner_machine

Sorry, running locally or outside of buildbot is hard. These scripts are made for automation. Please let us know if the wiki is out of date for anything else.

Does that solve your confusion? Can this bug be closed?

Comment 2

[Kartikaya Gupta (email:[e-mail])]

Ah, sorry - yes solves the problem I was seeing. My mistake for not reading the wiki page more carefully. Resolving this bug as invalid. Thanks for the quick response!