You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2023/10/27 00:49:00 UTC

[jira] [Reopened] (SPARK-45651) Snapshots of some packages are not published any more

     [ https://issues.apache.org/jira/browse/SPARK-45651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyukjin Kwon reopened SPARK-45651:
----------------------------------

Reverted in https://github.com/apache/spark/commit/df0262f29969fe40f53dee070a150f2bfe98484c

> Snapshots of some packages are not published any more
> -----------------------------------------------------
>
>                 Key: SPARK-45651
>                 URL: https://issues.apache.org/jira/browse/SPARK-45651
>             Project: Spark
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 4.0.0
>            Reporter: Enrico Minack
>            Assignee: Enrico Minack
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>
> Snapshots of some packages are not been published anymore, e.g. spark-sql_2.13-4.0.0 has not been published since Sep, 13th: https://repository.apache.org/content/groups/snapshots/org/apache/spark/spark-sql_2.13/4.0.0-SNAPSHOT/
> There have been some attempts to fix CI: SPARK-45535 SPARK-45536
> Assumption is that memory consumption during build exceeds the available memory of the Github host.
> The following could be attempted:
> - enable manual trigger of the {{publish_snapshots.yml}} workflow
> - enable some memory use logging to proof that exceeded memory is the root cause
> - attempt to reduce memory footprint and see impact in above logging
> - revert memory use logging



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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