Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The request was cancelled by the remote provider #9807

Closed
2 of 13 tasks
ramkia613 opened this issue May 8, 2024 · 2 comments
Closed
2 of 13 tasks

The request was cancelled by the remote provider #9807

ramkia613 opened this issue May 8, 2024 · 2 comments
Assignees
Labels
Area: Image administration bug report investigate Collect additional information, like space on disk, other tool incompatibilities etc. OS: Ubuntu

Comments

@ramkia613
Copy link

Description

Hi

GitHub actions jobs on my pipeline is canceled.

Note that some of the steps passed, and it's being canceled in the middle.

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • macOS 11
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

https://github.com/dee-money/passenger-android/actions/runs/8996691449/attempts/1

Is it regression?

no

Expected behavior

Job should pass

Actual behavior

Job starts, runs for quite a long time, part of the steps some job passed, and then in one of the steps is shown as "canceled".

Repro steps

It's a private repo

@shamil-mubarakshin
Copy link
Contributor

Hey @ramkia613, we will take a look

@Alexey-Ayupov
Copy link
Collaborator

Hello @ramkia613, We have checked the logs and found out that your run https://github.com/dee-money/passenger-android/actions/runs/8996691449/attempts/1 exhaust all available CPU and disk thruput resources on the runner.

In this case you have a several options:

  1. Adjust your workflow to minimize CPU and disk write operation load
  2. Switch to the larger runners
  3. Set up your own self-hosted runner

We will close this issue since we cannot do much about it, however if you have any other questions feel free to reach us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Image administration bug report investigate Collect additional information, like space on disk, other tool incompatibilities etc. OS: Ubuntu
Projects
None yet
Development

No branches or pull requests

3 participants