guyuqi commented on PR #1060:
URL: https://github.com/apache/bigtop/pull/1060#issuecomment-1333492563

   > @guyuqi Thanks for your review, but the smoke tests succeed on my machine 
for Fedora-36
   > 
   > ```
   > ./docker-hadoop.sh -d -C config_fedora-36.yaml --create 3 --memory 4g 
--repo file:///bigtop-home/output --disable-gpg-check --enable-local-repo 
--stack yarn,hdfs,spark --smoke-tests spark
   > ```
   > 
   > ```
   > Gradle Test Executor 2 started executing tests.
   > 
   > > Task :bigtop-tests:smoke-tests:spark:test
   > 
   > org.apache.bigtop.itest.spark.TestSpark > testSparkSQL STANDARD_OUT
   >     SPARK_MASTER isn't set. yarn will be used as the master URL. Refer to 
smoke-tests/README If this isn't what you you expect.
   > 
   > org.apache.bigtop.itest.spark.TestSpark > testSparkR STANDARD_OUT
   >     SPARK_MASTER isn't set. yarn will be used as the master URL. Refer to 
smoke-tests/README If this isn't what you you expect.
   > 
   > Gradle Test Executor 2 finished executing tests.
   > 
   > > Task :bigtop-tests:smoke-tests:spark:test
   > Finished generating test XML results (0.01 secs) into: 
/bigtop-home/bigtop-tests/smoke-tests/spark/build/test-results/test
   > Generating HTML test report...
   > Finished generating test html results (0.019 secs) into: 
/bigtop-home/bigtop-tests/smoke-tests/spark/build/reports/tests/test
   > Now testing...
   > :bigtop-tests:smoke-tests:spark:test (Thread[Execution worker for ':' 
Thread 2,5,main]) completed. Took 1 mins 20.387 secs.
   > 
   > BUILD SUCCESSFUL in 3m 21s
   > 30 actionable tasks: 7 executed, 23 up-to-date
   > Stopped 1 worker daemon(s).
   > + rm -rf buildSrc/build/test-results/binary
   > + rm -rf /bigtop-home/.gradle
   > ```
   
   The timeout of Spark smoke tests was expired. Maybe it caused by my limited 
hardware resource in my local host.(VM)
   Thank you for verify this PR on Fedora 36.  
   
   +1 LGTM. 


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

Reply via email to