zhengchenyu commented on PR #3292:
URL: https://github.com/apache/hive/pull/3292#issuecomment-1136682080

   > @zhengchenyu I am not sure what exactly do you mean by saying the unit 
tests are working in your environment. If you check the failed tests you will 
see a lot related to the `TestMiniLlapLocalCliDriver`. If you want to run these 
tests and update the plans you don't need Jenkins or anything else. You can do 
it by following the steps below:
   > 
   > ```
   > mvn clean install -DskipTests -Pitests
   > cd itests/qtest
   > mvn test -Dtest=TestMiniLlapLocalCliDriver -Dtest.output.overwrite
   > ```
   > 
   > If you want to run specific tests then you can use the `-Dqfile` option. 
For more info have a look here: 
https://cwiki.apache.org/confluence/display/Hive/HiveDeveloperFAQ#HiveDeveloperFAQ-HowdoIruntheclientpositive/clientnegativeunittests?
   
   @zabetak 
   
   In our compile server, I just test the uni-test in this way. Then all pass.
   Seems jenkins fail on this scripts. 
   ```
    # removes all stdout and err for passed tests
   xmlstarlet ed -L -d 'testsuite/testcase/system-out[count(../failure)=0]' -d 
'testsuite/testcase/system-err[count(../failure)=0]' `find . -name 'TEST*xml' 
-path '*/surefire-reports/*'`
   # remove all output.txt files
   find . -name '*output.txt' -path '*/surefire-reports/*' -exec unlink "{}" \\;
   ```
   
   I also execute this scripts, then pass. I don't know the difference between 
my compile server and this jenkins pipeline.
   
   Maybe I should setup a whole jenkins pipeline to reproduce this error. But 
jenkinsfile on my jenkins server run failed. 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to