Now that we have cpp unittests running from the test package, they can be removed from make check.

Is there anything else that needs to be done before we can turn these off?

Comment on attachment 8357147 [details] [diff] [review] Remove cpp unittests from make check I'm not sure sorry - ted should know though :-)

(In reply to Ed Morley [:edmorley UTC+0] from comment #2) > Comment on attachment 8357147 [details] [diff] [review] > Remove cpp unittests from make check > > I'm not sure sorry - ted should know though :-) Ed - no objections to turning these off soon then?

If the standalone suite does everything that the tests running as part of make check do, and the removal of this one make check target doesn't break anything from a releng POV (not sure what targets they run manually); then I'm really looking forward to this landing! :-) (Due to it saving cycles & reducing time before the build log ends up being uploaded & the build job visible in TBPL)

It will lose us our Win64 coverage on m-c, not that I actually care about that.

Comment on attachment 8357147 [details] [diff] [review] Remove cpp unittests from make check Review of attachment 8357147 [details] [diff] [review]: ----------------------------------------------------------------- The build config patch looks good. I'm not the correct person to sign off on the policy change and am not sure who is. But I would think if we don't lose any test coverage, there should be no concerns about the policy.

(In reply to Phil Ringnalda (:philor) from comment #5) > It will lose us our Win64 coverage on m-c, not that I actually care about > that. Are we not scheduling Win64 test jobs on m-c, or just not scheduling C++ unit test jobs? Either way, I suspect we can fix this in a followup.

Comment on attachment 8357147 [details] [diff] [review] Remove cpp unittests from make check Review of attachment 8357147 [details] [diff] [review]: ----------------------------------------------------------------- Policy shmolicy, this is a build config patch and you're completely qualified to review it. dminor has done the due diligence here--the tests are running in a separate job, he added "mach cppunittests", we're in good shape. I'll post to dev.platform to let people know about the change, but I don't expect any issues.

We're neither scheduling the tests on m-c nor keeping slaves running to take the jobs if we scheduled them: the ec2 instances we use for Win64 tests just die after a few days, and we resurrect them after a few months when someone wants to look at whichever twig it is where we are hypothetically greening them up, Date I think.

Comment on attachment 8357147 [details] [diff] [review] Remove cpp unittests from make check Thanks for the feedback. I did a try run here: https://tbpl.mozilla.org/?tree=Try&rev=a530f9bd4138

Thanks, pushed to https://hg.mozilla.org/integration/mozilla-inbound/rev/cc8ef74976b1

https://hg.mozilla.org/mozilla-central/rev/cc8ef74976b1 \m/