Setting up a new machine for local Base Runtime test rebuilds, I noticed the latest MBS (commit ba19f28878bbc26f047caf0fde6c401dacf26d92, 1.3.16) ignores my NUM_CONSECUTIVE_BUILDS setting and simply builds everything in one queue (well, actually it seems to create a new thread for every component build); this is a major regression for me as it slows down our local Base Runtime build by roughly 15 hours on average (make that 5 days for Bootstrap).

Our old machine runs c0cf9da84de8aa6c150eaa48d3f59f82381c24e5 which works fine in this regard; the drawback is it doesn't work with the production PDC and koji (due to its tag name check), uses the old dist tag scheme (breaking kernel builds) and apparently doesn't handle module inclusion (that might be broken in the latest release, too; hard to tell with it being so slow).

The logs of one such incomplete Bootstrap builds can be found here:
https://psabata.fedorapeople.org/m/module-bootstrap-master-20170325092014.tar.xz

My configuration changes from the default:

• KOJI_REPOSITORY_URL = 'file:///home/build/repos'
• PDC_URL = 'http://pdc.fedoraproject.org/rest_api/v1'
• SCMURLS = ["git://pkgs.fedoraproject.org/modules/"]
• MOCK_RESULTSDIR = '/home/build/results'
• DEFAULT_DIST_TAG_PREFIX = 'testbuild_'
• NUM_CONSECUTIVE_BUILDS = 36
• PKGDB_API_URL = 'https://admin.fedoraproject.org/pkgdb/api'
• LOG_BACKEND = 'file'
• LOG_LEVEL = 'debug'

I have the all the f26-modularity build downloaded in /home/build/repos/f26-modularity/latest/x86_64; I also have a module-bootstrap-master-1 symlink in /home/build/repos pointing to f26-modularity.

Please, fix this soon.