beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Wegner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-5717) [beam_PreCommit_Website_Stage_GCS_Cron] [stageWebsite] 404 The destination bucket gs://apache-beam-website-pull-requests does not exist or the write to the destination must be restarted
Date Thu, 11 Oct 2018 15:25:00 GMT

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

Scott Wegner commented on BEAM-5717:
------------------------------------

It appears the root-cause of this is that from the Jenkins job we attempt to pass a {{-PgithubPullRequestId}}
even when there is no associated PR (i.e. for the cron job). 

In the [Jenkins consoleFull|https://builds.apache.org/job/beam_PreCommit_Website_Stage_GCS_Cron/28/consoleFull]
log, I see the commandline:

{{$ /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Website_Stage_GCS_Cron/src/gradlew
--info --continue --max-workers=12 -Dorg.gradle.jvmargs=-Xms2g -Dorg.gradle.jvmargs=-Xmx4g
-PgithubPullRequestId=${ghprbPullId} :beam-website:stageWebsite}}

The easiest fix would probably be to remove the parameter from the Jenkins job if there is
no PR.

> [beam_PreCommit_Website_Stage_GCS_Cron] [stageWebsite] 404 The destination bucket gs://apache-beam-website-pull-requests
does not exist or the write to the destination must be restarted
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-5717
>                 URL: https://issues.apache.org/jira/browse/BEAM-5717
>             Project: Beam
>          Issue Type: Bug
>          Components: test-failures
>            Reporter: Scott Wegner
>            Assignee: Scott Wegner
>            Priority: Major
>              Labels: currently-failing
>
> _Use this form to file an issue for test failure:_
>  * [Jenkins Job|https://builds.apache.org/job/beam_PreCommit_Website_Stage_GCS_Cron/28/]
>  * [Gradle Build Scan|https://scans.gradle.com/s/3a7ujky4ekojw/console-log?task=:beam-website:stageWebsite#L4610]
>  * [Test source code|https://github.com/apache/beam/blob/280277e7788b4c28680dd8ca02d54a55195b24ba/website/build.gradle#L271]
> Initial investigation:
> I haven't seen this issue before; it's not clear if this is a persistent failure or a
flake. I will investigate further.
> ----
> _After you've filled out the above details, please [assign the issue to an individual|https://beam.apache.org/contribute/postcommits-guides/index.html#find_specialist].
Assignee should [treat test failures as high-priority|https://beam.apache.org/contribute/postcommits-policies/#assigned-failing-test],
helping to fix the issue or find a more appropriate owner. See [Apache Beam Post-Commit Policies|https://beam.apache.org/contribute/postcommits-policies]._



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message