Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL)
-
None
Description
main.mysql_binary_zero_insert [ fail ]
|
Test ended at 2021-11-07 18:30:21
|
|
CURRENT_TEST: main.mysql_binary_zero_insert
|
'grep' is not recognized as an internal or external command,
|
operable program or batch file.
|
mysqltest: At line 118: exec of 'C:\work\server\xxx\client\\Debug\mysqldump.exe --defaults-file=C:/work/server/xxx/mysql-test/var/my.cnf --defaults-group-suffix=.1 test tb --hex-blob | grep -A8 INSERT > C:/work/server/xxx/mysql-test/var/tmp/dump.sql' failed, error: 255, status: 255, errno: 2
|
Output from before failure:
|
# MYSQL_DUMP test tb --hex-blob | grep INSERT > MYSQL_TMP_DIR/dump.sql
|
Please, no tests with "exec grep" , without checking if grep indeed exists on the test machine.
If possible do
--source include/search_pattern_in_file.inc
Or replace grep with perl invocation, perl exists on the test box, obviously.
If even this is not possible (which I doubt), exclude this test from Windows.
The bug possibly exists prior to 10.7, I did not check.
Attachments
Issue Links
- is caused by
-
MDEV-25444 mysql --binary-mode is not able to replay some mysqlbinlog outputs
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue is caused by |
Affects Version/s | 10.2 [ 14601 ] | |
Affects Version/s | 10.3 [ 22126 ] | |
Affects Version/s | 10.4 [ 22408 ] | |
Affects Version/s | 10.5 [ 23123 ] | |
Affects Version/s | 10.6 [ 24028 ] |
Fix Version/s | 10.2 [ 14601 ] |
issue.field.resolutiondate | 2021-11-11 15:38:46.0 | 2021-11-11 15:38:46.794 |
Fix Version/s | 10.2.42 [ 26803 ] | |
Fix Version/s | 10.3.33 [ 26805 ] | |
Fix Version/s | 10.4.23 [ 26807 ] | |
Fix Version/s | 10.5.14 [ 26809 ] | |
Fix Version/s | 10.6.6 [ 26811 ] | |
Fix Version/s | 10.7.2 [ 26813 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 127107 ] | MariaDB v4 [ 159829 ] |
Pushed fix into 10.2.
Manual cherry-picking of the patch resulted in a merge conflict in 10.7, where 224f7a9 provides the resolution to this conflict.