-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-46302][TESTS] Skip maven daily testing as ivy uses some corrupted cache jar files #44208
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
Conversation
Done. |
.github/workflows/maven_test.yml
Outdated
required: false | ||
type: string | ||
default: '{}' | ||
default: '{"SKIP_SPARK_RELEASE_VERSIONS": "3.3.3,3.4.2,3.5.0,master"}' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need for master
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and default should be '{}'
or ''
, we should pass it from build_maven.yml
.github/workflows/maven_test.yml
Outdated
HIVE_PROFILE: ${{ matrix.hive }} | ||
SPARK_LOCAL_IP: localhost | ||
GITHUB_PREV_SHA: ${{ github.event.before }} | ||
SKIP_SPARK_RELEASE_VERSIONS: ${{ fromJSON(inputs.envs).SKIP_SPARK_RELEASE_VERSIONS }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This option should not be needed, the Run tests
section has already been deserialized for env
spark/.github/workflows/maven_test.yml
Lines 172 to 173 in 0b8e099
- name: Run tests | |
env: ${{ fromJSON(inputs.envs) }} |
.github/workflows/build_maven.yml
Outdated
with: | ||
envs: >- | ||
{ | ||
"SKIP_SPARK_RELEASE_VERSIONS": "3.3.3,3.4.2,3.5.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"SKIP_SPARK_RELEASE_VERSIONS": "3.3.3,3.4.2,3.5.0" | |
"SKIP_SPARK_RELEASE_VERSIONS": "3.3.4,3.4.2,3.5.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
I think we should make #44343 as TODO of this one, and explicitly add TODO in the code. On the other hand, please update the PR title and PR description to better match the change of this PR. |
maven's daily testing
skip some released spark versions, where ivy uses corrupted cache jars
maven's daily testing
skip some released spark versions, where ivy uses corrupted cache jars maven's daily testing
skip some released spark versions, where ivy uses corrupted cache jars
maven's daily testing
skip some released spark versions, where ivy uses corrupted cache jars maven's daily testing
skip some released spark versions, where ivy uses corrupted cache jars
maven's daily testing
skip some released spark versions, where ivy uses corrupted cache jars …ted cache jar files
Done. |
.github/workflows/build_and_test.yml
Outdated
npm install --save-dev | ||
node --experimental-vm-modules node_modules/.bin/jest | ||
maven-test: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fine to me, let's revert this change after test pass
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will revert this change, because the maven test has passed and the verification is successful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
} | ||
|
||
object PROCESS_TABLES extends QueryTest with SQLTestUtils { | ||
// TODO After SPARK-46400 and applying it to the already released Spark version, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm... I think maybe we can describe it like
In SPARK-46302, the env SKIP_SPARK_RELEASE_VERSIONS has been added to allow Maven tests to skip problematic release versions. Related issues will be fixed in SPARK-46400, and testing will be resumed after the fixed Spark 3.x version is released.
and I think just add comments here, no need to add them in line 247
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, let's run this test first.
in addition, before we release 3. x
, should we test test("backward compatibility")
after the SPARK-46400
feature is fixed on the branch master?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it has ever tested master...
I don't think it's necessary at the moment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before the fixed version released, Maven's daily tests can skip this case first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, LGTM
…ted cache jar files
Merged into master. Thanks @panbingkun Let's monitor next maven daily test ~ |
…maven repo, skip this cache and try again ### What changes were proposed in this pull request? The pr aims to - fix potential bug(ie: #44208) and enhance user experience. - make the code more compliant with standards ### Why are the changes needed? We use the local maven repo as the first-level cache in ivy. The original intention was to reduce the time required to parse and obtain the ar, but when there are corrupted files in the local maven repo,The above mechanism will be directly interrupted and the prompt is very unfriendly, which will greatly confuse the user. Based on the original intention, we should skip the cache directly in similar situations. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Manually test. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #44343 from panbingkun/SPARK-46400. Authored-by: panbingkun <pbk1982@gmail.com> Signed-off-by: Sean Owen <srowen@gmail.com>
…ocal maven repo, skip this cache and try again ### What changes were proposed in this pull request? The pr aims to - fix potential bug(ie: #44208) and enhance user experience. - make the code more compliant with standards Backport above to branch 3.5. Master branch pr: #44343 ### Why are the changes needed? We use the local maven repo as the first-level cache in ivy. The original intention was to reduce the time required to parse and obtain the ar, but when there are corrupted files in the local maven repo,The above mechanism will be directly interrupted and the prompt is very unfriendly, which will greatly confuse the user. Based on the original intention, we should skip the cache directly in similar situations. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Manually test. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #45017 from panbingkun/branch-3.5_SPARK-46400. Authored-by: panbingkun <panbingkun@baidu.com> Signed-off-by: yangjie01 <yangjie01@baidu.com>
…ocal maven repo, skip this cache and try again ### What changes were proposed in this pull request? The pr aims to - fix potential bug(ie: #44208) and enhance user experience. - make the code more compliant with standards Backport above to branch 3.4. Master branch pr: #44343 ### Why are the changes needed? We use the local maven repo as the first-level cache in ivy. The original intention was to reduce the time required to parse and obtain the ar, but when there are corrupted files in the local maven repo,The above mechanism will be directly interrupted and the prompt is very unfriendly, which will greatly confuse the user. Based on the original intention, we should skip the cache directly in similar situations. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Manually test. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #45018 from panbingkun/branch-3.4_SPARK-46400. Authored-by: panbingkun <panbingkun@baidu.com> Signed-off-by: Dongjoon Hyun <dhyun@apple.com>
…ocal maven repo, skip this cache and try again ### What changes were proposed in this pull request? The pr aims to - fix potential bug(ie: apache#44208) and enhance user experience. - make the code more compliant with standards Backport above to branch 3.4. Master branch pr: apache#44343 ### Why are the changes needed? We use the local maven repo as the first-level cache in ivy. The original intention was to reduce the time required to parse and obtain the ar, but when there are corrupted files in the local maven repo,The above mechanism will be directly interrupted and the prompt is very unfriendly, which will greatly confuse the user. Based on the original intention, we should skip the cache directly in similar situations. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Manually test. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#45018 from panbingkun/branch-3.4_SPARK-46400. Authored-by: panbingkun <panbingkun@baidu.com> Signed-off-by: Dongjoon Hyun <dhyun@apple.com>
What changes were proposed in this pull request?
The pr aims to skip maven daily testing as ivy uses some corrupted cache jar files.
This is a temporary workaround solution.
After SPARK-46400 and applying it to the already released Spark version, we should remove this logic.
Why are the changes needed?
Fix maven daily testing GA.


In our Maven daily testing, some UTs failed due to some corrupt jars in maven repo:
https://github.com/apache/spark/actions/runs/7019155617/job/19095991788#step:9:27263
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
No.