also fix unittest: test_profiles
notes: since the test won't read config files anymore, lift the loop number from 20 -> 256 to increase the probability of hitting the multithread issue
fixes: #1786
:thumbsup:
Is this two separate changes?
I don't think so. The test fails with this change
What I mean is that there is no explanation in the commit log about why we bump from 20 to 256 here.
20
256
rebased onto 0fd8e8beb431e29dbbbb8a1865ff564edc74965a
rebased onto 74065faa382ee5a5291d60de0cf4a349683a1c09
@ktdreyer the commit log updated
i see. Thanks.
Metadata Update from @julian8628: - Pull-request tagged with: testing-ready
Metadata Update from @jcupova: - Pull-request tagged with: testing-done
Commit 8f0efe89 fixes this pull-request
Pull-Request has been merged by tkopecek
also fix unittest: test_profiles
notes: since the test won't read config files anymore, lift the loop number from 20 -> 256 to increase the probability of hitting the multithread issue
fixes: #1786