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 2016/07/14 22:14:21 UTC

[jira] [Commented] (SPARK-16555) Work around Jekyll error-handling bug which led to silent doc build failures

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

Apache Spark commented on SPARK-16555:
--------------------------------------

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

> Work around Jekyll error-handling bug which led to silent doc build failures
> ----------------------------------------------------------------------------
>
>                 Key: SPARK-16555
>                 URL: https://issues.apache.org/jira/browse/SPARK-16555
>             Project: Spark
>          Issue Type: Bug
>          Components: Documentation, Project Infra
>            Reporter: Josh Rosen
>            Assignee: Josh Rosen
>
> If a custom Jekyll template tag throws Ruby's equivalent of a "file not found" exception, then Jekyll will stop the doc building process but will exit with a successful status, causing our doc publishing jobs to silently fail.
> This is caused by https://github.com/jekyll/jekyll/issues/5104, a case of bad error-handling logic in Jekyll. We should work around this in Spark to avoid more silent documentation build breaks.
> (See SPARK-16553 for an example of a build failure which was ignored due to this Jekyll bug).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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