Re: --create-testdir speed

Tim Rice wrote: > > +@noindent > > +(You can't do this will all of Gnulib at once: @code{gnulib-tool} would run > Thanks; fixed: 2024-03-05 Bruno Haible doc: Fix a typo. Reported by Tim Rice in

Re: --create-testdir speed

On Sun, 3 Mar 2024, Bruno Haible wrote: > +@example > +gnulib-tool --create-megatestdir --with-tests --dir=... autobuild MODULES > +@end example > + > +@noindent > +(You can't do this will all of Gnulib at once: @code{gnulib-tool} would run I assume the brain wanted to t

Re: --create-testdir speed

Collin Funk wrote: > > --create-megatestdir with all modules is not realistic: it would consume > > hundreds of GB of disk space and maybe a week of run time. > > > > --create-megatestdir is useful for a small set of modules, in particular > > for 2 modules, e.g. fnmatch-posix and fnmatch-gnu. >

Re: --create-testdir speed

On 3/1/24 6:13 AM, Bruno Haible wrote: > On an ASUS UX305CA-FC093T (a notebook) from 2017, I remember that it took > about 45 minutes. On the Fujitsu ESPRIMO G7012A that I own now, it takes > about 17 minutes. That sounds similar to my experience. > --create-megatestdir with all modules is not re

Re: --create-testdir speed

Collin Funk wrote: > How long does gnulib-tool --create-testdir and --create-megatestdir > usually take with all modules, if you can remember? On an ASUS UX305CA-FC093T (a notebook) from 2017, I remember that it took about 45 minutes. On the Fujitsu ESPRIMO G7012A that I own now, it takes about 17