-
Bug
-
Resolution: Fixed
-
P4
-
8
-
b01
-
windows
The test compares the output of native2ascii with a file containing the correct answers.
The native2ascii output uses CR, NL for line breaks on Windows, while the correct file uses NL.
When comparing, CR is removed from the native2ascii output.
However, the sed command used to remove CR is incorrect.
'sed -e 's@\\r@@g'' replaces the literal \r, but to remove CR, it should be 'sed -e 's@\r@@g''.
Environment:
Intel(R) Xeon(R) Platinum 8260 CPU 2.4GHz, 2 core, 8GB Memory
Windows 10 Enterprise
The native2ascii output uses CR, NL for line breaks on Windows, while the correct file uses NL.
When comparing, CR is removed from the native2ascii output.
However, the sed command used to remove CR is incorrect.
'sed -e 's@\\r@@g'' replaces the literal \r, but to remove CR, it should be 'sed -e 's@\r@@g''.
Environment:
Intel(R) Xeon(R) Platinum 8260 CPU 2.4GHz, 2 core, 8GB Memory
Windows 10 Enterprise
- links to
-
Commit(master) openjdk/jdk8u-dev/21e4278a
-
Review(master) openjdk/jdk8u-dev/400