HeartSaVioR commented on pull request #29017:
URL: https://github.com/apache/spark/pull/29017#issuecomment-655544712
I hope we do the migration iteratively - we all know it became a huge pain
to see the green light of the build (rarely possible according to the Jenkins
PRB build trends),
HeartSaVioR commented on pull request #29017:
URL: https://github.com/apache/spark/pull/29017#issuecomment-655146331
I also saw two cases today - sharing one:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/125258/console
HeartSaVioR commented on pull request #29017:
URL: https://github.com/apache/spark/pull/29017#issuecomment-654587394
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/buildTimeTrend
While unidoc/dependency look to be back to normal, still lots of PR builds
are
HeartSaVioR commented on pull request #29017:
URL: https://github.com/apache/spark/pull/29017#issuecomment-654543116
I roughly remember we tried once and it didn't work well. Does anyone
remember why, and which PR was the attempt?
HeartSaVioR commented on pull request #29017:
URL: https://github.com/apache/spark/pull/29017#issuecomment-654503533
OK, using the same profiles in Github Action as we do in PRB looks to be
tricky. If it's possible then I think Github Action can replace the gendoc in
PRB, but if not we
