Skip to content

[MINOR] improvement(test): Disable Spark UI for Spark integration tests #1831

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 26, 2024

Conversation

wForget
Copy link
Member

@wForget wForget commented Jun 25, 2024

What changes were proposed in this pull request?

Disable Spark UI for Spark integration tests.

Why are the changes needed?

Spark UI is not necessary for test cases.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Existing UTs.

Copy link

Test Results

 2 640 files   - 9   2 640 suites   - 9   5h 24m 4s ⏱️ - 3m 14s
   945 tests ±0     943 ✅  -  1   1 💤 ±0  0 ❌ ±0  1 🔥 +1 
11 772 runs   - 9  11 756 ✅  - 10  15 💤 ±0  0 ❌ ±0  1 🔥 +1 

For more details on these errors, see this check.

Results for commit 74562c5. ± Comparison against base commit 30cefcc.

@rickyma rickyma changed the title [MINOR] refactor: Disable spark ui for spark integration test base [MINOR] refactor: Disable Spark UI for Spark integration tests Jun 25, 2024
Copy link
Contributor

@rickyma rickyma left a comment

Choose a reason for hiding this comment

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

Thanks. LGTM.

@rickyma rickyma changed the title [MINOR] refactor: Disable Spark UI for Spark integration tests [MINOR] improvement(test): Disable Spark UI for Spark integration tests Jun 25, 2024
@rickyma rickyma merged commit f8e4329 into apache:master Jun 26, 2024
41 of 43 checks passed
@rickyma
Copy link
Contributor

rickyma commented Jun 26, 2024

Merged to master. Thanks @wForget

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants