gecko-dev/browser/config/mozconfigs/linux32/rusttests

MOZ_AUTOMATION_BUILD_SYMBOLS=0
MOZ_AUTOMATION_PACKAGE_TESTS=0
MOZ_AUTOMATION_L10N_CHECK=0

mk_add_options MOZ_MAKE_FLAGS=--output-sync=line

. "$topsrcdir/browser/config/mozconfigs/linux32/nightly"

unset ENABLE_CLANG_PLUGIN
Bug 1373878 - part 4 - mozharness and mozconfigs for rusttest builds; r=chmanchester We need mozharness configurations and mozconfigs for rusttests. We are explicitly not doing Windows debug configurations currently because of peculiar link errors in such configurations. 2017-10-02 16:21:22 +03:00			`MOZ_AUTOMATION_BUILD_SYMBOLS=0`
			`MOZ_AUTOMATION_PACKAGE_TESTS=0`
			`MOZ_AUTOMATION_L10N_CHECK=0`

Bug 1505072 - Automation and mozconfig changes to convert rusttests builds to use non-default build target. r=froydnj Two mozconfg additions are necessary for these jobs on linux: 1.) Turning off the clang plugin, which will not get built during these builds and will cause failures when C/C++ needed by the rust build tries to find it. 2.) Adding --output-sync=line to our make invocation: at some point the "export" phase started relying on this, and it's missing because the non-default build targets invoked by the rusttests builds don't go through client.mk. Differential Revision: https://phabricator.services.mozilla.com/D11242 --HG-- extra : moz-landing-system : lando 2018-11-08 21:38:26 +03:00			`mk_add_options MOZ_MAKE_FLAGS=--output-sync=line`
Bug 1373878 - part 4 - mozharness and mozconfigs for rusttest builds; r=chmanchester We need mozharness configurations and mozconfigs for rusttests. We are explicitly not doing Windows debug configurations currently because of peculiar link errors in such configurations. 2017-10-02 16:21:22 +03:00
			`. "$topsrcdir/browser/config/mozconfigs/linux32/nightly"`
Bug 1505072 - Automation and mozconfig changes to convert rusttests builds to use non-default build target. r=froydnj Two mozconfg additions are necessary for these jobs on linux: 1.) Turning off the clang plugin, which will not get built during these builds and will cause failures when C/C++ needed by the rust build tries to find it. 2.) Adding --output-sync=line to our make invocation: at some point the "export" phase started relying on this, and it's missing because the non-default build targets invoked by the rusttests builds don't go through client.mk. Differential Revision: https://phabricator.services.mozilla.com/D11242 --HG-- extra : moz-landing-system : lando 2018-11-08 21:38:26 +03:00
			`unset ENABLE_CLANG_PLUGIN`