Tim Skirvin

At the very least I don't see any errors, so this is progress! I'll have to spend some time making sure everything still works. Will you be uploading to pip?

8192.pp - puppet-lint $i 1771.98s user 3.81s system 99% cpu 29:36.13 total Note that I acknowledge that the easiest answer to this problem is "don't do this", and I have...

puppet parser validate: 1.pp - puppet parser validate $i 1.39s user 0.12s system 99% cpu 1.524 total 2.pp - puppet parser validate $i 1.39s user 0.13s system 99% cpu 1.527...

Note that you can witness the same speed with an empty manifest. Just add a few thousand blank lines to your manifest, and you'll speed puppet-lint down immediately.

Do you know when the next release is going to be?

It's out! So, new numbers: 1.pp - puppet-lint $i 0.15s user 0.03s system 88% cpu 0.207 total 2.pp - puppet-lint $i 0.16s user 0.03s system 99% cpu 0.195 total 4.pp...

``` 1.pp - puppet-lint $i 0.16s user 0.02s system 98% cpu 0.187 total 2.pp - puppet-lint $i 0.15s user 0.04s system 99% cpu 0.191 total 4.pp - puppet-lint $i 0.11s...

Any word? This is fairly critical to our firewall use case.

For what it's worth, my solution to this problem was to abandon firewalld entirely. nftables has treated me better.

Can this get unblocked? I'm starting to use this module now, and the whole "whole puppet run crashes" thing sure looks like a show-stopper.