This is an automated email from the ASF dual-hosted git repository.
gurwls223 pushed a commit to branch branch-3.0
in repository https://gitbox.apache.org/repos/asf/spark.git
The following commit(s) were added to refs/heads/branch-3.0 by this push:
new ae75095 [SPARK-34951][INFRA][PYTHON][TESTS] Set the system encoding
as UTF-8 to recover the Sphinx build in GitHub Actions
ae75095 is described below
commit ae750959c05c31c78f58322d7ed3c508597f55af
Author: HyukjinKwon <[email protected]>
AuthorDate: Sun Apr 4 16:22:57 2021 +0900
[SPARK-34951][INFRA][PYTHON][TESTS] Set the system encoding as UTF-8 to
recover the Sphinx build in GitHub Actions
This PR proposes to set the system encoding as UTF-8. For some reasons, it
looks like GitHub Actions machines changed theirs to ASCII by default. This
leads to default encoding/decoding to use ASCII in Python, e.g.)
`"a".encode()`, and looks like Sphinx depends on that.
To recover GItHub Actions build.
No, dev-only.
Tested in https://github.com/apache/spark/pull/32046
Closes #32047 from HyukjinKwon/SPARK-34951.
Authored-by: HyukjinKwon <[email protected]>
Signed-off-by: HyukjinKwon <[email protected]>
(cherry picked from commit 82ad2f9dff9b8d9cb8b6b166f14311f6066681c2)
Signed-off-by: HyukjinKwon <[email protected]>
---
.github/workflows/build_and_test.yml | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/.github/workflows/build_and_test.yml
b/.github/workflows/build_and_test.yml
index eac3ff7..f453b43 100644
--- a/.github/workflows/build_and_test.yml
+++ b/.github/workflows/build_and_test.yml
@@ -273,6 +273,9 @@ jobs:
lint:
name: Linters, licenses, dependencies and documentation generation
runs-on: ubuntu-20.04
+ env:
+ LC_ALL: C.UTF-8
+ LANG: C.UTF-8
container:
image: dongjoon/apache-spark-github-action-image:20201025
steps:
@@ -342,8 +345,6 @@ jobs:
- name: Run documentation build
run: |
cd docs
- export LC_ALL=C.UTF-8
- export LANG=C.UTF-8
jekyll build
java-11:
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
