Hi Sofia, On Fri, Aug 17, 2018 at 4:51 PM, Sofia Carrillo <secarrill...@gmail.com> wrote:
> Hello all, > > My name is Sofia, and I was an intern this summer on the Build Systems > team. Some developers have shown interest in the work I was doing this > summer, so I wanted to share this with you in case you found the > information useful. > > One of the tools I worked on generates a report that can spit out the most > "expensive" files (those which change frequently and significantly impact > build times) of the tree. If you are interested in getting your hands on > this report, instructions can be found below. > > Though my internship has ended, please feel free to contact me with any > questions. I hope these tools are useful and can provide some insight! Also > feel free to contact either mshal or chmanchester in #build. > > Instructions to generate the report: > https://docs.google.com/presentation/d/1dhfMGhFbevkoOShjyhlB > hpWyNT49MkpifHgq2292yR4/edit?usp=sharing > > My presentation slides (for more context of my project): > https://docs.google.com/presentation/d/1V0C6xKrHyTrJAFkSLGXd > m3DpEfJqkjsV1VLcyp9QxgQ/edit?usp=sharing > This is really interesting work; thanks for doing it and distributing it! I have a question about the slide about "expensive files in the last 30 days on m-c". I see `python/mozversioncontrol/mozversioncontrol/__init__.py` in the table. That's not an "expensive input" in my mind. Can you explain how that's entering the expense calculations? Thanks, Nick
_______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
