Re: To what extent is sccache's distributed compilation usable?

As announced in this week's project call, sccache-dist schedulers have been deployed to mozilla offices, and those with hardware available can enroll servers based on the documentation here .

Proposal: build-id generation in developer builds

Our build-id is currently compiled in to libxul, and is re-generated with every build invocation. To avoid re-linking libxul with every build invocation we have some Makefile hacks in place to hide the build dependency between libxul and the buildid. As part of improving the build system we'd

Re: Build System Project - Update from the last 2 weeks

Hi Armen, Thanks for noticing that, I think you found an issue with how we're submitting data caused by something I landed last week. I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1266183 to track a fix. Chris On Wed, Apr 20, 2016 at 12:01 PM, Armen Zambrano G.

Re: PSA: Requiring annotations for test support files required by multiple test directories

t-file > for tests are being requested? > > Thanks, > Jared > > On Tue, Mar 29, 2016 at 12:55 PM, Christopher Manchester < > chmanches...@gmail.com> wrote: > >> As you may know, manifestparser test manifests (mochitest.ini, >> browser.ini and co.) conta

PSA: Requiring annotations for test support files required by multiple test directories

As you may know, manifestparser test manifests (mochitest.ini, browser.ini and co.) contain a "support-files" field informing the build system certain files in the tree or generated at build time are required by tests. These files are currently installed to the objdir for some test flavors and

GTests are now running on test machines

GTests are now run from their own job on Treeherder instead of during the build in "make check'. They can be found under the "GTest" symbol on treeherder on all integration branches, and can be added to try pushes with "-u gtest" (they will run with "-u all"). As an effect of this change we're

Prioritizing tests based on file changes

Some tests are more likely than others to fail in response to a given change, but our automation does little to optimize based on this. As a result, test automation frequently runs more than necessary for a given push, leading to excess load on automation and time spent waiting for the results of

Re: It is now possible to apply arbitrary tags to tests/manifests and run all tests with a given tag

). On Tue, Mar 31, 2015 at 10:57 AM, Christopher Manchester chmanches...@gmail.com wrote: I filed bug 1149670 for the mach try feature. On Tue, Mar 31, 2015 at 10:39 AM, Andrew Halberstadt ahalberst...@mozilla.com wrote: It's technically already possible by modifying the in-tree mozharness

Re: It is now possible to apply arbitrary tags to tests/manifests and run all tests with a given tag

...@mozilla.com wrote: On Thursday, April 30, 2015 at 7:22:26 PM UTC-4, Christopher Manchester wrote: You can now add --tag arguments to try syntax and they will get passed to test harnesses in your try push. Details of the implementation are in bug 978846, but if you're interested

Re: It is now possible to apply arbitrary tags to tests/manifests and run all tests with a given tag

, 2015 at 7:22:26 PM UTC-4, Christopher Manchester wrote: You can now add --tag arguments to try syntax and they will get passed to test harnesses in your try push. Details of the implementation are in bug 978846, but if you're interested in passing other arguments from try syntax

Re: It is now possible to apply arbitrary tags to tests/manifests and run all tests with a given tag

You can now add --tag arguments to try syntax and they will get passed to test harnesses in your try push. Details of the implementation are in bug 978846, but if you're interested in passing other arguments from try syntax to a test harness, this can be done by adding those arguments to

Retiring the monolithic test package

This message is about bug 917999 - Split test package into per-suite packages, more can be found there. I'm working on a set of patches to do this, but the assumption that a build comes with a tests.zip that has all of the tests to run against that build seems likely to be a part of more tools

Re: It is now possible to apply arbitrary tags to tests/manifests and run all tests with a given tag

I filed bug 1149670 for the mach try feature. On Tue, Mar 31, 2015 at 10:39 AM, Andrew Halberstadt ahalberst...@mozilla.com wrote: It's technically already possible by modifying the in-tree mozharness configs here: https://dxr.mozilla.org/mozilla-central/source/testing/config/mozharness

Structured Logging update

Myself and others on Automation and Tools have undertaken an effort to convert our test harnesses to use structured logging. We are making this conversion to allow our testing infrastructure to move away from regex based log parsing and to expose more useful log data (with a focus on test results