
Load_entry_point('mozregression=0.6.4', 'console_scripts', 'mozregression')()įile "build/bdist.macosx-10.8-intel/egg/mozregression/regression.py", line 187, in cliįile "build/bdist.macosx-10.8-intel/egg/mozregression/regression.py", line 105, in bisectįile "build/bdist.macosx-10.8-intel/egg/mozregression/regression.py", line 96, in printRangeįile "build/bdist.macosx-10.8-intel/egg/mozregression/regression.py", line 87, in buildįile "build/bdist.macosx-10.8-intel/egg/mozregression/regression.py", line 81, in findRegressionChsetįile "/Library/Python/2.7/site-packages/mozcommitbuilder-0.4.11-py2.7.egg/mozcommitbuilder/builder.py", line 304, in bisect Nonzero exit code from įile "/usr/local/bin/mozregression", line 8, in Summary: Merge mozilla-central into services-centralĮxception RuntimeError: RuntimeError('maximum recursion depth exceeded in _instancecheck_',) in ignored Summary: Bug 850450 - Longitudinal recording of build ID in FHR r=rnewman
/cdn.vox-cdn.com/assets/2226951/6v02-24_16-39-0740.jpg)
Summary: Bug 837292 - Part 4: Followup to unbust part 2 r=rnewman XXX files update, X files merged, XX files removed, X files unresolved Testing changeset XXX (209 changeset remaing, ~7 tests)

Hg -R /Users/mbp1/.moz-commitbuilder-cache/mozbuild-trunk bisect -skip I'm just a bit skeptical on build, started 15 minutes ago, that continue to report: Yes mozregression acts any necessary actions once you've installed mercurial. > right tools are installed, so no manual process should be needed. > As far as i know mozregression offers to do the neccessary steps when the > how to bisect and find the real causing changeset: > Once you have installed mercurial, here you can find more information about > (In reply to m.fabbri from comment #10) > (In reply to MarioMi (:MarioMi) from comment #13)

(In reply to Georg Fritzsche from comment #17) In nightly version all works fine instead in the immediately following version appears the reported error.ĭo you want to bisect further by fetching the repository and building? (y or n) y Was this nightly good, bad, or broken? (type 'good', 'bad', 'skip', 'retry', or 'exit' and press Enter): JVMLauncher.afterStart(): starting JVM process watcherĬould not kill process, could not find pid: 963, assuming it's already dead MacBook-Pro-di-mbp1:~ mbp1$ mozregression -good= Ok I've used mozregression tool on my MacOS X (10.8.3) with Java 7u21 and this the results:
