Skip to content

Conversation

@dongjoon-hyun
Copy link
Member

@dongjoon-hyun dongjoon-hyun commented Jul 26, 2020

What changes were proposed in this pull request?

Two different versions are used for the same artifacts, exec-maven-plugin and scalatest-maven-plugin. This PR aims to use the same versions for exec-maven-plugin and scalatest-maven-plugin. In addition, this PR removes scala-maven-plugin.version from K8s integration suite because it's unused.

Why are the changes needed?

This will prevent the mistake which upgrades only one place and forgets the others.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Pass the Jenkins K8S IT.

<exec-maven-plugin.version>1.4.0</exec-maven-plugin.version>
<extraScalaTestArgs></extraScalaTestArgs>
<kubernetes-client.version>4.9.2</kubernetes-client.version>
<scala-maven-plugin.version>3.2.2</scala-maven-plugin.version>
Copy link
Member Author

@dongjoon-hyun dongjoon-hyun Jul 26, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is unused.

@SparkQA
Copy link

SparkQA commented Jul 26, 2020

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

@SparkQA
Copy link

SparkQA commented Jul 26, 2020

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

@dongjoon-hyun
Copy link
Member Author

Actually, this PR's change passed Jenkins K8s IT because it triggers all tests successfully. The one test case failure is irrelevant and flaky one.

KubernetesSuite:
- Run SparkPi with no resources *** FAILED ***
  The code passed to eventually never returned normally. Attempted 190 times over 3.0022143221666666 minutes. Last failure message: false was not true. (KubernetesSuite.scala:388)
- Run SparkPi with a very long application name.
- Use SparkLauncher.NO_RESOURCE
- Run SparkPi with a master URL without a scheme.
- Run SparkPi with an argument.
- Run SparkPi with custom labels, annotations, and environment variables.
- All pods have the same service account by default
- Run extraJVMOptions check on driver
- Run SparkRemoteFileTest using a remote data file
- Run SparkPi with env and mount secrets.
- Run PySpark on simple pi.py example
- Run PySpark with Python3 to test a pyfiles example
- Run PySpark with memory customization
- Run in client mode.
- Start pod creation from template
- PVs with local storage
- Launcher client dependencies
- Test basic decommissioning
Run completed in 15 minutes, 37 seconds.
Total number of tests run: 18
Suites: completed 2, aborted 0
Tests: succeeded 17, failed 1, canceled 0, ignored 0, pending 0
*** 1 TEST FAILED ***

@dongjoon-hyun
Copy link
Member Author

Retest this please.

<artifactId>spark-kubernetes-integration-tests_2.12</artifactId>
<properties>
<download-maven-plugin.version>1.3.0</download-maven-plugin.version>
<exec-maven-plugin.version>1.4.0</exec-maven-plugin.version>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is outdated.

<extraScalaTestArgs></extraScalaTestArgs>
<kubernetes-client.version>4.9.2</kubernetes-client.version>
<scala-maven-plugin.version>3.2.2</scala-maven-plugin.version>
<scalatest-maven-plugin.version>1.0</scalatest-maven-plugin.version>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is outdated.

@SparkQA
Copy link

SparkQA commented Jul 27, 2020

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

@SparkQA
Copy link

SparkQA commented Jul 27, 2020

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

@dongjoon-hyun
Copy link
Member Author

  1. GitHub Actions passed (except SparkR due to [SPARK-32451][R] Support Apache Arrow 1.0.0 #29252 ).
  2. K8s IT already passed at the first attempt. The second K8s IT attempt failed with the following minikube issue.
stderr: error execution phase certs/etcd-server: failed to write certificate "etcd-server": failure loading etcd/server certificate: failed to load certificate: the certificate has expired
: Process exited with status 1

@dongjoon-hyun
Copy link
Member Author

Hi, @liyinan926 . Could you review this K8s IT dependency change PR? This PR upgrades the old versions and refactors them in order to avoid being outdate again.

@dongjoon-hyun
Copy link
Member Author

Retest this please.

@dongjoon-hyun
Copy link
Member Author

dongjoon-hyun commented Jul 27, 2020

Hi, @HyukjinKwon and @viirya . Could you review this PR? This is simply in order to update the dependency by removing the duplications. And, it's tested already but it's retriggered due to the flakiness in K8s minikube installation in Jenkins.

@dongjoon-hyun
Copy link
Member Author

dongjoon-hyun commented Jul 27, 2020

Thank you so much, @HyukjinKwon .
Merged to master/3.0

@dongjoon-hyun
Copy link
Member Author

Oh, Thank you, @viirya , too!

@SparkQA
Copy link

SparkQA commented Jul 27, 2020

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

@SparkQA
Copy link

SparkQA commented Jul 27, 2020

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

@dongjoon-hyun
Copy link
Member Author

For a record, the following is the K8s minikube starts failure log.

+ minikube --vm-driver=kvm2 start --memory 6000 --cpus 8
There is a newer version of minikube available (v1.12.1).  Download it here:
https://github.com/kubernetes/minikube/releases/tag/v1.12.1

To disable this notification, run the following:
minikube config set WantUpdateNotification false
o   minikube v0.34.1 on linux (amd64)
i   Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
:   Re-using the currently running kvm2 VM for "minikube" ...
:   Waiting for SSH access ...
-   "minikube" IP address is 192.168.39.69
-   Configuring Docker as the container runtime ...
-   Preparing Kubernetes environment ...
-   Pulling images required by Kubernetes v1.13.3 ...
:   Relaunching Kubernetes v1.13.3 using kubeadm ... 
!   Error restarting cluster: running cmd: sudo kubeadm init phase certs all --config /var/lib/kubeadm.yaml: command failed: sudo kubeadm init phase certs all --config /var/lib/kubeadm.yaml
stdout: [certs] Using certificateDir folder "/var/lib/minikube/certs/"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk

stderr: error execution phase certs/apiserver-kubelet-client: failed to write certificate "apiserver-kubelet-client": failure loading apiserver-kubelet-client certificate: failed to load certificate: the certificate has expired
: Process exited with status 1

*   Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
-   https://github.com/kubernetes/minikube/issues/new

dongjoon-hyun added a commit that referenced this pull request Jul 27, 2020
…alatest-maven-plugin

### What changes were proposed in this pull request?

Two different versions are used for the same artifacts, `exec-maven-plugin` and `scalatest-maven-plugin`. This PR aims to use the same versions for `exec-maven-plugin` and `scalatest-maven-plugin`. In addition, this PR removes `scala-maven-plugin.version` from `K8s` integration suite because it's unused.

### Why are the changes needed?

This will prevent the mistake which upgrades only one place and forgets the others.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Pass the Jenkins K8S IT.

Closes #29248 from dongjoon-hyun/SPARK-32448.

Authored-by: Dongjoon Hyun <[email protected]>
Signed-off-by: Dongjoon Hyun <[email protected]>
(cherry picked from commit 13c64c2)
Signed-off-by: Dongjoon Hyun <[email protected]>
@dongjoon-hyun dongjoon-hyun deleted the SPARK-32448 branch July 27, 2020 05:33
@SparkQA
Copy link

SparkQA commented Jul 27, 2020

Test build #126585 has finished for PR 29248 at commit 39021ee.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Jul 27, 2020

Test build #126590 has finished for PR 29248 at commit 39021ee.

  • This patch fails due to an unknown error code, -9.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Jul 27, 2020

Test build #126600 has finished for PR 29248 at commit 39021ee.

  • This patch fails due to an unknown error code, -9.
  • This patch merges cleanly.
  • This patch adds no public classes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants