| Bug #36923 | Test "nist_all" needs its result file updated | ||
|---|---|---|---|
| Submitted: | 23 May 2008 17:21 | ||
| Reporter: | Joerg Bruehe | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Tests: Server | Severity: | S3 (Non-critical) |
| Version: | 5.0.62 | OS: | Any |
| Assigned to: | Matthias Leich | CPU Architecture: | Any |
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.053 sec. using MySQL 8.4.5-u7-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
© 2025, Oracle Corporation and/or its affiliates
Description: Found in the release build of 5.0.62. Test "nist_all" fails in all runs on all platforms, because the server now does not issue a warning which is not expected by the test author(s) anyway - but it is still contained in the ".result" file. (Analysis done by Matthias). The difference is like this: ===== nist_all [ fail ] --- /PATH/mysql-test/suite/nist/r/nist_all.result +++ /PATH/mysql-test/suite/nist/r/nist_all.reject @@ -12009,8 +12009,6 @@ DELETE FROM CH1; INSERT INTO CH1 VALUES ('FOO', 'F', 'BLANKS '); -Warnings: -Note 1265 Data truncated for column 'CH1C' at row 1 affected rows: 1 SELECT CH1A, CH1B, CH1C FROM CH1; mysqltest: Result content mismatch ===== How to repeat: Get the NIST suite and run it. Suggested fix: Status is "closed", because Matthias already pushed the corrected result file.