Actually, the slowest part of the build is when the core unit tests complete and it goes to run the failsafe tests. I think it scans all the unit tests looking for the tests to run as there is a very long pause where nothing happens. I want to break these tests out to a separate project as that should cut the build time noticably.
Ralph > On Jan 7, 2017, at 7:22 PM, Matt Sicker <boa...@gmail.com> wrote: > > Added. I also noticed that we have build.html on the site as well as > BUILDING.adoc in the root. Maybe if we can use the same file format on both, > we can use a symlink or something? > > On 7 January 2017 at 19:27, Remko Popma <remko.po...@gmail.com > <mailto:remko.po...@gmail.com>> wrote: > > On Jan 8, 2017, at 10:26, Remko Popma <remko.po...@gmail.com > <mailto:remko.po...@gmail.com>> wrote: > >> Maybe in the "building Log4j2 from source" page? > https://github.com/apache/logging-log4j2/blob/master/src/site/xdoc/build.xml.vm > > <https://github.com/apache/logging-log4j2/blob/master/src/site/xdoc/build.xml.vm> >> >> Sent from my iPhone >> >> On Jan 8, 2017, at 10:23, Gary Gregory <garydgreg...@gmail.com >> <mailto:garydgreg...@gmail.com>> wrote: >> >>> Where should we doc this? >>> >>> Gary >>> >>> On Jan 7, 2017 3:32 PM, "Matt Sicker" <boa...@gmail.com >>> <mailto:boa...@gmail.com>> wrote: >>> Turns out that if you're missing /etc/hosts entries for your machine's host >>> name, then InetAddress.getLocalHost() needs to do a lot of DNS lookups to >>> determine what IP addresses are associated to your hostname. If you're on >>> IPv6, this could end up as a rather large list, too, which takes a while to >>> look them up the first time. Considering >>> LoggerContext.setConfiguration(Configuration) calls this method, it can >>> significantly increase test execution time if you don't have an /etc/hosts >>> entry for your computer. >>> >>> -- >>> Matt Sicker <boa...@gmail.com <mailto:boa...@gmail.com>> > > > > -- > Matt Sicker <boa...@gmail.com <mailto:boa...@gmail.com>>
