You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/10/28 10:09:00 UTC

[GitHub] [shardingsphere-elasticjob] TeslaCN opened a new issue #1671: An error may occur in ScriptJobExecutorTestl when using Windows environment

TeslaCN opened a new issue #1671:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1671


   ## Bug Report
   
   ### Actual behavior
   
   ```
   -------------------------------------------------------
    T E S T S
   -------------------------------------------------------
   Running org.apache.shardingsphere.elasticjob.script.ScriptJobExecutorTest
   Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.327 sec <<< FAILURE! - in org.apache.shardingsphere.elasticjob.script.ScriptJobExecutorTest
   assertProcess(org.apache.shardingsphere.elasticjob.script.ScriptJobExecutorTest)  Time elapsed: 0.261 sec  <<< ERROR!
   org.apache.shardingsphere.elasticjob.infra.exception.JobSystemException: Execute script failure.
           at org.apache.shardingsphere.elasticjob.script.ScriptJobExecutorTest.assertProcess(ScriptJobExecutorTest.java:82)
   
   
   Results :
   
   Tests in error:
     ScriptJobExecutorTest.assertProcess:82 ? JobSystem Execute script failure.
   
   Tests run: 4, Failures: 0, Errors: 1, Skipped: 0
   
   [INFO] ------------------------------------------------------------------------
   [INFO] Reactor Summary for elasticjob 3.0.0-beta:
   [INFO]
   [INFO] elasticjob ......................................... SUCCESS [  9.502 s]
   [INFO] elasticjob-api ..................................... SUCCESS [  7.516 s]
   [INFO] elasticjob-infra ................................... SUCCESS [  1.546 s]
   [INFO] elasticjob-infra-common ............................ SUCCESS [ 15.722 s]
   [INFO] elasticjob-registry-center ......................... SUCCESS [ 26.175 s]
   [INFO] elasticjob-restful ................................. SUCCESS [ 28.959 s]
   [INFO] elasticjob-ecosystem ............................... SUCCESS [  2.459 s]
   [INFO] elasticjob-tracing ................................. SUCCESS [  0.752 s]
   [INFO] elasticjob-tracing-api ............................. SUCCESS [ 32.285 s]
   [INFO] elasticjob-error-handler ........................... SUCCESS [  0.861 s]
   [INFO] elasticjob-error-handler-spi ....................... SUCCESS [  4.219 s]
   [INFO] elasticjob-error-handler-type ...................... SUCCESS [  0.851 s]
   [INFO] elasticjob-error-handler-general ................... SUCCESS [ 10.688 s]
   [INFO] elasticjob-executor ................................ SUCCESS [  1.260 s]
   [INFO] elasticjob-executor-kernel ......................... SUCCESS [ 13.654 s]
   [INFO] elasticjob-executor-type ........................... SUCCESS [  1.015 s]
   [INFO] elasticjob-simple-executor ......................... SUCCESS [ 11.463 s]
   [INFO] elasticjob-dataflow-executor ....................... SUCCESS [ 12.028 s]
   [INFO] elasticjob-script-executor ......................... FAILURE [  5.964 s]
   ```
   
   ### Reason analyze (If you can)
   
   ### Steps to reproduce the behavior.
   
   ### Example codes for reproduce this issue (such as a github link).
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere-elasticjob] terrymanu closed issue #1671: An error may occur in ScriptJobExecutorTestl when using Windows environment

Posted by GitBox <gi...@apache.org>.
terrymanu closed issue #1671:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1671


   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org