[DO NOT MERGE] Try the new Github action process

[gengliangwang]

Let's verify the new process from #32092

[gengliangwang]

GA starts: https://github.com/gengliangwang/spark/actions/runs/747046279

[SparkQA]

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41903/

[dongjoon-hyun]

Thank you, @gengliangwang . :)

[dongjoon-hyun]

BTW, just a question, for the failed GA, only the owner can re-trigger it because it's running on his repo, @HyukjinKwon and @gengliangwang ?

[HyukjinKwon]

Ah.. good point. Yeah ..

[HyukjinKwon]

Suggested change

	checkAnswer(queryCoalesce, Row("2") :: Nil)
	checkAnswer(queryCoalesce, Row("2") :: Nil)

[HyukjinKwon]

In the worst case (e.g., author is inactive but PR is ready .. ?), we could push an empty commit to their branch to retrigger .. of course this is an ugly way though

[SparkQA]

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41903/

[gengliangwang]

BTW, just a question, for the failed GA, only the owner can re-trigger it because it's running on his repo, @HyukjinKwon and @gengliangwang ?

In the worst case (e.g., author is inactive but PR is ready .. ?), we could push an empty commit to their branch to retrigger .. of course this is an ugly way though

That's true.
How about having a backdoor that triggers the test in Apache/Spark upon certain comments? Similar to what we did for Jenkins: "ok to test"/"retest this please"

[HyukjinKwon]

I'm not sure if that's feasible or not but that would be great to have it.

[Ngone51]

I can't see the comment from github-actions as it did in HyukjinKwon#34. Is it supposed to comment after testing finished or only in certain cases?

[HyukjinKwon]

The comment will be added by "Notify test workflow" job later. There are too many jobs in the queue so it's not triggered yet ...

[Ngone51]

Got it, thanks @HyukjinKwon

[SparkQA]

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41909/

[SparkQA]

Test build #137323 has finished for PR 32158 at commit 9536df2.

• This patch fails Spark unit tests.
• This patch merges cleanly.
• This patch adds no public classes.

[SparkQA]

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41909/

[SparkQA]

Test build #137329 has finished for PR 32158 at commit 9536df2.

• This patch fails Spark unit tests.
• This patch merges cleanly.
• This patch adds no public classes.

[github-actions]

Test build #747046279 for PR 32158 at commit 9536df2.

[SparkQA]

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41945/

[SparkQA]

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41945/

[SparkQA]

Test build #137367 has finished for PR 32158 at commit 8a79b5e.

• This patch fails Spark unit tests.
• This patch merges cleanly.
• This patch adds no public classes.

[github-actions]

Test build #749195392 for PR 32158 at commit edf2178.

[github-actions]

Test build #749195392 for PR 32158 at commit 8a79b5e.

[github-actions]

Test build #755330484 for PR 32158 at commit fc61869.

[SparkQA]

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42058/

[SparkQA]

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42058/

[SparkQA]

Test build #137483 has finished for PR 32158 at commit fc61869.

• This patch fails Spark unit tests.
• This patch merges cleanly.
• This patch adds no public classes.

[dongjoon-hyun]

Do we need to test this more, @gengliangwang ?

[gengliangwang]

It should be fine now. Let me close it.