I wrote:
> Aleksander Alekseev writes:
>> Alternatively we could get rid of
>> ENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS entirely since its practical
>> value seems to be debatable.
> Strong -1 on that, for the reason given above.
Perhaps an alternative could be to expend some more sweat on the
Aleksander Alekseev writes:
>> When looking at a patch in the CFBot I realized that the SSL tests generate
>> backend warnings under ENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS
> Good catch. I can confirm that the patch corrects the named WARNINGs
> appearing with:
> CPPFLAGS="-DENFORCE_REGRESSION_
Hi,
> When looking at a patch in the CFBot I realized that the SSL tests generate
> backend warnings under ENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS
Good catch. I can confirm that the patch corrects the named WARNINGs
appearing with:
CPPFLAGS="-DENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS"
There
When looking at a patch in the CFBot I realized that the SSL tests generate
backend warnings under ENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS due to roles
and databases not following the regression test naming convention. While not
impacting the tested functionality, it's pretty silly to have warni
