You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Alex Amato <aj...@google.com> on 2020/08/19 03:23:24 UTC

Still seeing these wheel build emails on my fork

Asked about this a few weeks ago, I rebased from master as was suggested,
but I am still seeing these. I am guessing this is wasting our resources
somehow? :(


On Tue, Aug 18, 2020 at 7:28 PM Alex Amato <no...@github.com> wrote:

> Run failed for master (010adc5)
>
> Repository: ajamato/beam
> Workflow: Build python wheels
> Duration: 8 minutes and 20.0 seconds
> Finished: 2020-08-19 02:28:43 UTC
>
> View results <https://github.com/ajamato/beam/actions/runs/214541528>
> Jobs:
>
>    - build_source <https://github.com/ajamato/beam/runs/1001143594>
>    succeeded (0 annotations)
>    - Build wheels on ubuntu-latest
>    <https://github.com/ajamato/beam/runs/1001149597> cancelled (2
>    annotations)
>    - Build wheels on macos-latest
>    <https://github.com/ajamato/beam/runs/1001149606> failed (1 annotation)
>    - Build wheels on windows-latest
>    <https://github.com/ajamato/beam/runs/1001149615> cancelled (2
>    annotations)
>    - Prepare GCS <https://github.com/ajamato/beam/runs/1001149638>
>    skipped (0 annotations)
>    - Upload source to GCS bucket
>    <https://github.com/ajamato/beam/runs/1001149658> skipped (0
>    annotations)
>    - Tag repo nightly <https://github.com/ajamato/beam/runs/1001159805>
>    skipped (0 annotations)
>    - Upload wheels to GCS bucket
>    <https://github.com/ajamato/beam/runs/1001159822> skipped (0
>    annotations)
>    - List files on Google Cloud Storage Bucket
>    <https://github.com/ajamato/beam/runs/1001159835> skipped (0
>    annotations)
>
> —
> You are receiving this because this workflow ran on your branch.
> Manage your GitHub Actions notifications here
> <https://github.com/settings/notifications>.
>

Re: Still seeing these wheel build emails on my fork

Posted by Alex Amato <aj...@google.com>.
Thanks, done

On Tue, Aug 18, 2020 at 8:49 PM Rui Wang <ru...@google.com> wrote:

> I solved this by disabling github actions in my forked repo:
> https://github.community/t/how-to-turn-off-github-actions-for-a-repo/16875
>
>
> -Rui
>
> On Tue, Aug 18, 2020 at 8:23 PM Alex Amato <aj...@google.com> wrote:
>
>> Asked about this a few weeks ago, I rebased from master as was suggested,
>> but I am still seeing these. I am guessing this is wasting our resources
>> somehow? :(
>>
>>
>> On Tue, Aug 18, 2020 at 7:28 PM Alex Amato <no...@github.com>
>> wrote:
>>
>>> Run failed for master (010adc5)
>>>
>>> Repository: ajamato/beam
>>> Workflow: Build python wheels
>>> Duration: 8 minutes and 20.0 seconds
>>> Finished: 2020-08-19 02:28:43 UTC
>>>
>>> View results <https://github.com/ajamato/beam/actions/runs/214541528>
>>> Jobs:
>>>
>>>    - build_source <https://github.com/ajamato/beam/runs/1001143594>
>>>    succeeded (0 annotations)
>>>    - Build wheels on ubuntu-latest
>>>    <https://github.com/ajamato/beam/runs/1001149597> cancelled (2
>>>    annotations)
>>>    - Build wheels on macos-latest
>>>    <https://github.com/ajamato/beam/runs/1001149606> failed (1
>>>    annotation)
>>>    - Build wheels on windows-latest
>>>    <https://github.com/ajamato/beam/runs/1001149615> cancelled (2
>>>    annotations)
>>>    - Prepare GCS <https://github.com/ajamato/beam/runs/1001149638>
>>>    skipped (0 annotations)
>>>    - Upload source to GCS bucket
>>>    <https://github.com/ajamato/beam/runs/1001149658> skipped (0
>>>    annotations)
>>>    - Tag repo nightly <https://github.com/ajamato/beam/runs/1001159805>
>>>    skipped (0 annotations)
>>>    - Upload wheels to GCS bucket
>>>    <https://github.com/ajamato/beam/runs/1001159822> skipped (0
>>>    annotations)
>>>    - List files on Google Cloud Storage Bucket
>>>    <https://github.com/ajamato/beam/runs/1001159835> skipped (0
>>>    annotations)
>>>
>>> —
>>> You are receiving this because this workflow ran on your branch.
>>> Manage your GitHub Actions notifications here
>>> <https://github.com/settings/notifications>.
>>>
>>

Re: Still seeing these wheel build emails on my fork

Posted by Rui Wang <ru...@google.com>.
I solved this by disabling github actions in my forked repo:
https://github.community/t/how-to-turn-off-github-actions-for-a-repo/16875


-Rui

On Tue, Aug 18, 2020 at 8:23 PM Alex Amato <aj...@google.com> wrote:

> Asked about this a few weeks ago, I rebased from master as was suggested,
> but I am still seeing these. I am guessing this is wasting our resources
> somehow? :(
>
>
> On Tue, Aug 18, 2020 at 7:28 PM Alex Amato <no...@github.com>
> wrote:
>
>> Run failed for master (010adc5)
>>
>> Repository: ajamato/beam
>> Workflow: Build python wheels
>> Duration: 8 minutes and 20.0 seconds
>> Finished: 2020-08-19 02:28:43 UTC
>>
>> View results <https://github.com/ajamato/beam/actions/runs/214541528>
>> Jobs:
>>
>>    - build_source <https://github.com/ajamato/beam/runs/1001143594>
>>    succeeded (0 annotations)
>>    - Build wheels on ubuntu-latest
>>    <https://github.com/ajamato/beam/runs/1001149597> cancelled (2
>>    annotations)
>>    - Build wheels on macos-latest
>>    <https://github.com/ajamato/beam/runs/1001149606> failed (1
>>    annotation)
>>    - Build wheels on windows-latest
>>    <https://github.com/ajamato/beam/runs/1001149615> cancelled (2
>>    annotations)
>>    - Prepare GCS <https://github.com/ajamato/beam/runs/1001149638>
>>    skipped (0 annotations)
>>    - Upload source to GCS bucket
>>    <https://github.com/ajamato/beam/runs/1001149658> skipped (0
>>    annotations)
>>    - Tag repo nightly <https://github.com/ajamato/beam/runs/1001159805>
>>    skipped (0 annotations)
>>    - Upload wheels to GCS bucket
>>    <https://github.com/ajamato/beam/runs/1001159822> skipped (0
>>    annotations)
>>    - List files on Google Cloud Storage Bucket
>>    <https://github.com/ajamato/beam/runs/1001159835> skipped (0
>>    annotations)
>>
>> —
>> You are receiving this because this workflow ran on your branch.
>> Manage your GitHub Actions notifications here
>> <https://github.com/settings/notifications>.
>>
>