Bug #100853 Wrong parameter "explicit_default_wait_counter" in "innodb.tablespace_encrypt_*"

• Submitted: 15 Sep 2020 9:55
• Modified: 25 Sep 2020 5:35
• Reporter: Przemysław Skibiński (OCA)
• Status: Duplicate
• Category: MySQL Server: Tests
• Severity: S7 (Test Cases)
• Version: 8.0.21
• OS: Any
• CPU Architecture: Any

[15 Sep 2020 9:55] Przemysław Skibiński

Description:
"include/wait_until_connected_again.inc" uses the "explicit_default_counter" parameter, not "explicit_default_wait_counter" as defined

--let $explicit_default_wait_counter=10000;

in the following files

mysql-test/suite/auth_sec/t/keyring_udf.test
mysql-test/suite/innodb/t/table_encrypt_fts.test
mysql-test/suite/innodb/t/tablespace_encrypt_1.test
mysql-test/suite/innodb/t/tablespace_encrypt_2.test
mysql-test/suite/innodb/t/tablespace_encrypt_3.test
mysql-test/suite/innodb/t/tablespace_encrypt_4.test
mysql-test/suite/innodb/t/tablespace_encrypt_5.test
mysql-test/suite/innodb/t/tablespace_encrypt_6.test
mysql-test/suite/innodb/t/tablespace_encrypt_7.test
mysql-test/suite/innodb/t/tablespace_encrypt_8.test
mysql-test/suite/innodb/t/tablespace_encrypt_9.test

There is also a typo ("explict" instead of "explicit")

--let $explict_default_wait_counter=10000 

in mysql-test/suite/innodb/t/mysql_ts_alter_encrypt_1.test

How to repeat:
Search for all occurrences of "default_wait_counter"

Suggested fix:
Replace "explicit_default_wait_counter" with "explicit_default_counter"

[15 Sep 2020 11:26] MySQL Verification Team

Hello Przemysław,

Thank you for the report and feedback.

regards,
Umesh

[25 Sep 2020 5:35] Erlend Dahl

Duplicate of

Bug#100542 Confusion: $explicit_default_wait_counter and $explicit_default_counter

which has been fixed in the upcoming 8.0.22. The solution was to standardize on $explicit_default_wait_counter.

The typo in mysql-test/suite/innodb/t/mysql_ts_alter_encrypt_1.test wasn't noticed though, we will fix that.