Solid tip from Xidorn. For the lazy, that command is: ./mach mozregression --launch b5a512aaef49 --repo try
On 2018-04-20 9:53 AM, Xidorn Quan wrote: > FWIW, I always find that the easiest way to run some build is using > mozregression's "Run a single build", which would take care of downloading, > unpacking, and creating a new profile for it. > > In this case, you'd want to choose "try" and input changeset "b5a512aaef49". > > - Xidorn > > On Fri, Apr 20, 2018, at 6:12 PM, Carl Corcoran wrote: >> Hello everyone! I need some help gathering some real-world data about DLLs >> that get loaded into Firefox on Windows (re bug 1435827). I have created a >> test build that outputs runtime DLL information to a text file on disk, and >> I'd like to see what results you get on your machine(s). >> >> If you have already helped me with this, no need to do it again. >> >> So when you have a moment, can you please: >> >> 1. Make sure you have a c:\temp directory >> 2. Download target.zip from either of the links below, extract, & run >> firefox.exe >> - for 64-bit, https://treeherder.mozilla.org/logviewer.html#?job_id= >> 174270831&repo=try >> - for 32-bit, https://treeherder.mozilla.org/logviewer.html#?job_id= >> 174270829&repo=try >> 3. Run it at least for a while. The idea is to get a profile of DLLs >> that are loaded into the process. >> 4. Find the results at c:\temp\ffmodules.txt, and email them to me at >> [email protected] > _______________________________________________ > dev-platform mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-platform >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
