Uh oh!
There was an error while loading. Please reload this page.
[SPARK-3479] [Build] Report failed test category - #2606
Conversation
nchammas
commented
Sep 30, 2014
I'm gonna post several test commits here to try out the various failure modes and confirm that they are reported correctly. |
0f6dcd3 to
cc243c9CompareSparkQA
commented
Sep 30, 2014
QA tests have started for PR 2606 at commit
|
SparkQA
commented
Sep 30, 2014
QA tests have finished for PR 2606 at commit
|
AmplabJenkins
commented
Sep 30, 2014
Test FAILed. |
AmplabJenkins
commented
Sep 30, 2014
Test FAILed. |
AmplabJenkins
commented
Oct 1, 2014
Test FAILed. |
nchammas
commented
Oct 1, 2014
Jenkins failed to checkout the patch. Jenkins, retest this please. |
nchammas
commented
Oct 1, 2014
Jenkins, retest this please. |
AmplabJenkins
commented
Oct 1, 2014
Test FAILed. |
nchammas
commented
Oct 1, 2014
Jenkins, retest this please. |
SparkQA
commented
Oct 1, 2014
QA tests have started for PR 2606 at commit
|
SparkQA
commented
Oct 1, 2014
QA tests have finished for PR 2606 at commit
|
AmplabJenkins
commented
Oct 1, 2014
Test FAILed. |
AmplabJenkins
commented
Oct 1, 2014
Test FAILed. |
nchammas
commented
Oct 1, 2014
Grr, Jenkins flakiness checking out stuff from git... Oi Jenkins! Retest this please. |
nchammas
commented
Oct 1, 2014
Jenkins, retest this please. |
SparkQA
commented
Oct 1, 2014
QA tests have started for PR 2606 at commit
|
SparkQA
commented
Oct 1, 2014
QA tests have finished for PR 2606 at commit
|
AmplabJenkins
commented
Oct 1, 2014
Test FAILed. |
SparkQA
commented
Oct 1, 2014
QA tests have started for PR 2606 at commit
|
SparkQA
commented
Oct 1, 2014
QA tests have started for PR 2606 at commit
|
SparkQA
commented
Oct 1, 2014
QA tests have finished for PR 2606 at commit
|
AmplabJenkins
commented
Oct 1, 2014
Test FAILed. |
SparkQA
commented
Oct 1, 2014
QA tests have finished for PR 2606 at commit
|
AmplabJenkins
commented
Oct 1, 2014
Test FAILed. |
SparkQA
commented
Oct 1, 2014
QA tests have started for PR 2606 at commit
|
SparkQA
commented
Oct 1, 2014
QA tests have finished for PR 2606 at commit
|
AmplabJenkins
commented
Oct 1, 2014
Test FAILed. |
SparkQA
commented
Oct 1, 2014
QA tests have started for PR 2606 at commit
|
SparkQA
commented
Oct 1, 2014
QA tests have finished for PR 2606 at commit
|
AmplabJenkins
commented
Oct 1, 2014
Test FAILed. |
nchammas
commented
Oct 1, 2014
Hmm, I expected a failure in the PySpark doctests, not here. |
nchammas
commented
Oct 1, 2014
Jenkins, retest this please. |
AmplabJenkins
commented
Oct 1, 2014
Test FAILed. |
nchammas
commented
Oct 1, 2014
Another checkout timeout. |
nchammas
commented
Oct 1, 2014
Jenkins, retest this please. |
SparkQA
commented
Oct 1, 2014
QA tests have started for PR 2606 at commit
|
SparkQA
commented
Oct 1, 2014
QA tests have finished for PR 2606 at commit
|
AmplabJenkins
commented
Oct 1, 2014
Test FAILed. |
f137249 to
d67df03CompareSparkQA
commented
Oct 1, 2014
QA tests have started for PR 2606 at commit
|
SparkQA
commented
Oct 1, 2014
QA tests have finished for PR 2606 at commit
|
AmplabJenkins
commented
Oct 1, 2014
Test PASSed. |
nchammas
commented
Oct 2, 2014
cc @pwendell This PR is ready for review. Here are examples of the messages posted when: |
There was a problem hiding this comment.
We can do a valid diff regardless of the merge-ability of the patch, so I moved this out of the if block.
JoshRosen
commented
Oct 2, 2014
This looks great! Thanks for adding the extra comments to explain the |
nchammas
commented
Oct 6, 2014
@pwendell@JoshRosen Is this PR ready to be merged in? |
JoshRosen
commented
Oct 6, 2014
Sure, this looks fine to me so I'm going to merge it now. Thanks! |
…h modern GitHub Actions grouping ### What changes were proposed in this pull request? Remove the old `CURRENT_BLOCK` and `ERROR_CODES` testing infrastructure and replace it with an updated `titled_block` context manager that also groups log output on GitHub Actions. Move section titles from the various helper functions into titled blocks in `main()`. Exit codes are no longer driven by the old blocks. If the tests fail, the script exits with a non-zero code, usually `1`. Make sure that titled blocks cannot be nested, and that all large blocks of output have a suitable title block at the top level `main()` function. That means I moved the following checks and calls up to `main()`: - `run_java_style_checks` - `build_spark_unidoc_sbt` - `SKIP_PACKAGING` flag check - `SKIP_UNIDOC` flag check Fold `group_in_github_actions` into the new `titled_block`. Remove `build_spark_documentation`, which is not used by anything. ### Why are the changes needed? Amusingly, I added this testing infrastructure 12 years ago in #2606 (later refactored into Python in #5694). It was built for Jenkins, which we do not use anymore. The block and error codes are not used by any part of our current test infrastructure on GitHub Actions. The new `titled_block` context manager takes care of printing block titles as before, and also subsumes the log grouping behavior from `group_in_github_actions` (introduced in #54524) since it is useful for more than just sbt. We have a [separate job for building the docs][docs], so I assume we don't want to revive the currently-dead `build_spark_documentation`. [docs]: https://github.com/apache/spark/blob/2e83cd8444d787203ed2e594f78a1c54bfcaff42/.github/workflows/build_and_test.yml#L1218-L1240 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? CI for this PR. Some illustrative screenshots of the new log groups: <img width="375" src="https://github.com/user-attachments/assets/80da8dff-15a5-4569-b224-580d7bf029de" /> <img width="286" src="https://github.com/user-attachments/assets/32469a0c-77bf-44f9-ac16-c3a12662fcc7" /> The purple debug lines are from my fork and are not related to this PR. ### Was this patch authored or co-authored using generative AI tooling? I wrote this with assistance from GitHub Copilot. Closes#57770 from nchammas/run-tests-titled-block. Authored-by: Nicholas Chammas <nicholas.chammas@gmail.com> Signed-off-by: Nicholas Chammas <nicholas.chammas@gmail.com>
…h modern GitHub Actions grouping ### What changes were proposed in this pull request? Remove the old `CURRENT_BLOCK` and `ERROR_CODES` testing infrastructure and replace it with an updated `titled_block` context manager that also groups log output on GitHub Actions. Move section titles from the various helper functions into titled blocks in `main()`. Exit codes are no longer driven by the old blocks. If the tests fail, the script exits with a non-zero code, usually `1`. Make sure that titled blocks cannot be nested, and that all large blocks of output have a suitable title block at the top level `main()` function. That means I moved the following checks and calls up to `main()`: - `run_java_style_checks` - `build_spark_unidoc_sbt` - `SKIP_PACKAGING` flag check - `SKIP_UNIDOC` flag check Fold `group_in_github_actions` into the new `titled_block`. Remove `build_spark_documentation`, which is not used by anything. ### Why are the changes needed? Amusingly, I added this testing infrastructure 12 years ago in #2606 (later refactored into Python in #5694). It was built for Jenkins, which we do not use anymore. The block and error codes are not used by any part of our current test infrastructure on GitHub Actions. The new `titled_block` context manager takes care of printing block titles as before, and also subsumes the log grouping behavior from `group_in_github_actions` (introduced in #54524) since it is useful for more than just sbt. We have a [separate job for building the docs][docs], so I assume we don't want to revive the currently-dead `build_spark_documentation`. [docs]: https://github.com/apache/spark/blob/2e83cd8444d787203ed2e594f78a1c54bfcaff42/.github/workflows/build_and_test.yml#L1218-L1240 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? CI for this PR. Some illustrative screenshots of the new log groups: <img width="375" src="https://github.com/user-attachments/assets/80da8dff-15a5-4569-b224-580d7bf029de" /> <img width="286" src="https://github.com/user-attachments/assets/32469a0c-77bf-44f9-ac16-c3a12662fcc7" /> The purple debug lines are from my fork and are not related to this PR. ### Was this patch authored or co-authored using generative AI tooling? I wrote this with assistance from GitHub Copilot. Closes#57770 from nchammas/run-tests-titled-block. Authored-by: Nicholas Chammas <nicholas.chammas@gmail.com> Signed-off-by: Nicholas Chammas <nicholas.chammas@gmail.com> (cherry picked from commit cef67d7) Signed-off-by: Nicholas Chammas <nicholas.chammas@gmail.com>
This PR allows SparkQA (i.e. Jenkins) to report in its posts to GitHub what category of test failed, if one can be determined.
The failure categories are:
This PR also fixes the diffing logic used to determine if a patch introduces new classes.