Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
0.13.0
-
None
-
Windows 8 using Hive Monarch build environment
Description
If you create a .q.out file on Windows using a command like this:
ant test "-Dhadoop.security.version=1.1.0-SNAPSHOT" "-Dhadoop.root=c:\hw\project\hadoop-monarch" "-Dresolvers=internal" "-Dhadoop-0.20S.version=1.1.0-SNAPSHOT" "-Dhadoop.mr.rev=20S" "-Dhive.support.concurrency=false" "-Dshims.include=0.20S" "-Dtest.continue.on.failure=true" "-Dtest.halt.on.failure=no" "-Dtest.print.classpath=true" "-Dtestcase=TestCliDriver" "-Dqfile=vectorized_math_funcs.q,vectorized_string_funcs.q,vectorized_casts.q" "-Doverwrite=true" "-Dtest.silent=false"
Then the .q.out files generated in the hive directory under
ql\src\test\results\clientpositive
having missing blank lines.
So, the .q tests will pass on your Windows machine. But when you upload them in a patch, they fail on the automated build server. See HIVE-5517 for an example. HIVE-5517.3.patch has .q.out files with missing blank lines. Hive-5517.4.patch has .q.out files created on a Linux or Mac system. Those have blank lines.
Attachments
Attachments
Issue Links
- is related to
-
HIVE-5178 Wincompat : QTestUtil changes
- Resolved