4 Commits (master)

Author	SHA1	Message	Date
Guillem Jover	a9166843c2	TT#71952 Parallelize templated output generation ... Switch away from the old daemon/wrapper architecture, which complicates things and requires more scaffolding code. We turn the daemon/wrapper and build_config into a single perl process that will load all YAML files, and then process each input/output pair on a parallel child, to try to speed up the processing as much as possible. For whole rebuilds, it might speed up the generation by at least a factor of x2, x4 or more, depending on the number of active processors. Change-Id: I51aa2f90336e34a20983d8733f45b64d9b6fea0b	5 years ago
Guillem Jover	b2c87aa4a9	TT#47373 Remove path hardcoding for hooks handling ... When running the test suite, in case we need to cover the code paths that are handling the hooks, we should not assume the files are installed in the system directories. Change-Id: I1cd09eaf186d28093eb03ad5e9fc096fe7d63a3e	7 years ago
Guillem Jover	50ecc15441	TT#37401 Use Unix sockets to avoid relying on hostnames for localhost/loopback ... If the file /etc/hosts gets handled by templates, as ongoing changes attempt to do, there's a problem because /etc/hosts gets truncated to create a new file when it's needed to generate itself, to resolve the "localhost" string as hostname, so the generation fails and /etc/hosts gets empty at that point, affecting the system until restored. The simplest way to break that cycle is to switch to Unix sockets. Change-Id: I1e33ead6a134625346b9cf1beb09a7bdbfdfc8d2	7 years ago
Michael Prokop	29e8c96162	TT#26206 Provide README for working with tests ... Especially when working on tests for new features it's useful to run ngcpcfg and pytest interchangeably. Since identifying all relevant variables is annoying let's provide an example command line that's known to being useful while working on the "ngcpcfg patch" tests. Change-Id: I1ae1499ba2607f553d1dddcb355c7a3758d1a844	7 years ago