Bug 1325148 - Temporarily disable leakchecking in crashtests on linux, r=jmaher

This is being disabled because of the leak in bug 1325215. It slipped in because leak
checking in reftest was temporarily failing to turn the job orange. We are disabling
leak checking so we can land the fix ASAP and prevent further bustage from slipping
through in the mean time. Once bug 1325215 has been fixed, this should be backed out.

MozReview-Commit-ID: 74VGhHvZtIG

--HG--
extra : rebase_source : 176dd020bb13947198c52378be86463e69f7749b
This commit is contained in:
Andrew Halberstadt 2016-12-21 17:06:29 -05:00
parent 88fcee124a
commit b0448cc0a9

View File

@ -369,7 +369,17 @@ class RefTest(object):
# Enable leaks detection to its own log file.
self.leakLogFile = os.path.join(profileDir, "runreftest_leaks.log")
browserEnv["XPCOM_MEM_BLOAT_LOG"] = self.leakLogFile
# Leak checking was broken in reftest unnoticed for a length of time. During
# this time, a leak slipped into the crashtest suite. The leak checking was
# fixed by bug 1325148, but it couldn't land until the regression in crashtest
# was also fixed or backed out. Rather than waiting and risking new regressions,
# temporarily disable leak checking in crashtest. Fix is tracked by bug 1325215.
if options.suite == 'crashtest' and mozinfo.info['os'] == 'linux':
self.log.warning('WARNING | leakcheck disabled due to bug 1325215')
else:
browserEnv["XPCOM_MEM_BLOAT_LOG"] = self.leakLogFile
return browserEnv
def killNamedOrphans(self, pname):