You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2022/04/20 08:32:00 UTC

[jira] [Commented] (SPARK-38966) Fix CI for fork branches in-sync with upstream master

    [ https://issues.apache.org/jira/browse/SPARK-38966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524802#comment-17524802 ] 

Apache Spark commented on SPARK-38966:
--------------------------------------

User 'EnricoMi' has created a pull request for this issue:
https://github.com/apache/spark/pull/36263

> Fix CI for fork branches in-sync with upstream master
> -----------------------------------------------------
>
>                 Key: SPARK-38966
>                 URL: https://issues.apache.org/jira/browse/SPARK-38966
>             Project: Spark
>          Issue Type: Improvement
>          Components: Project Infra
>    Affects Versions: 3.4.0
>            Reporter: Enrico Minack
>            Priority: Major
>
> Whenever I sync my fork master from upstream Apache master, CI fails: https://github.com/G-Research/spark/runs/5972229542?check_suite_focus=true
> ```
> From https://github.com/G-Research/spark
>  * branch                  master     -> FETCH_HEAD
> Already up to date. (nothing to squash)
> On branch master
> Your branch is up to date with 'origin/master'.
> nothing to commit, working tree clean
> Error: Process completed with exit code 1.
> ```
> Since my fork master is without changes, the `git commit` fails. This is annoying.
> The same issue makes the scheduled build and test workflow fail multiple times a day.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org