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

GitHub Action step is hanging until timeout #6704

Closed
2 of 11 tasks
mattyrob opened this issue Dec 6, 2022 · 8 comments
Closed
2 of 11 tasks

GitHub Action step is hanging until timeout #6704

mattyrob opened this issue Dec 6, 2022 · 8 comments
Assignees
Labels
Area: JavaScript and Node.js bug report investigate Collect additional information, like space on disk, other tool incompatibilities etc. OS: Ubuntu

Comments

@mattyrob
Copy link

mattyrob commented Dec 6, 2022

Description

An GitHub action to run QUnit tests that has worked well for some time stopped working around the 22nd of November. The process runs on Linux using ubuntu-latest.
On finding this blog article we have specified the workflow to use ubuntu-20-04 and the workflow is now operational again.

See also report I made in the wrong repository:
actions/runner#2298

Platforms affected

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

Runner images affected

  • Ubuntu 18.04
  • Ubuntu 20.04
  • Ubuntu 22.04
  • macOS 10.15
  • macOS 11
  • macOS 12
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

2.299.1

https://github.com/ClassicPress/ClassicPress/actions/runs/3542477755/jobs/5948017123

Is it regression?

https://github.com/ClassicPress/ClassicPress/actions/runs/3521742250/jobs/5903925683

Expected behavior

This QUnit test should continue to work and function to completeness without hanging

Actual behavior

The process runs as expected until the final step where the process hangs without further log output until the process is terminated after running without completing at 6 hours.

Repro steps

Update the current GitHub Actions configuration to use ubuntu-latest and run the action.
Process will reach last stage and hang for 6 hours until being terminated.

On ubuntu-20.04 the process runs successfully.

@Alexey-Ayupov Alexey-Ayupov added OS: Ubuntu investigate Collect additional information, like space on disk, other tool incompatibilities etc. labels Dec 6, 2022
@erik-bershel
Copy link
Contributor

Probably related to this #6698. I'll be more specific after a little research.

@Alexey-Ayupov
Copy link
Collaborator

Please provide minimal repro steps.

@mattyrob
Copy link
Author

mattyrob commented Dec 6, 2022

The workflow file affected is here:
https://github.com/ClassicPress/ClassicPress/blob/develop/.github/workflows/javascript-tests.yml

You may be able to see from the run history that we started getting run failures about 2 weeks ago (22 Nov 2022).

The workflow was using runs-on: ubuntu-latest and I noted in this blog that specifying a version would help if processes broke. I therefore tried runs-on: ubuntu-20.04 and the task began running to completion once again.

To reproduce I suppose you could:
1/ clone the repository
2/ amend the workflow to use ubuntu-latest again
3/ run the workflow manually

@khider
Copy link

khider commented Dec 15, 2022

Same problem. installing the dependencies hangs and eventually times out. Tried to downgrade to Ubuntu-20.04 as suggested above but it didn't fix the problem.

Link to repo: https://github.com/LinkedEarth/Pyleoclim_util/actions/runs/3707003131/jobs/6282898422

@MaksimZhukov
Copy link
Contributor

Hello @mattyrob!
Sorry for the late response and thank you for your patience!
I've tried to reproduce the issue on a clean Ubuntu 22.04 VM and got the same result - test step hangs. It seems to me that your project is not compatible with Ubuntu 22.04 or the issue is related to Ubuntu 22.04 itself.
Have you tried running the tests locally on Ubuntu 22.04?

@mattyrob
Copy link
Author

@MaksimZhukov - thanks for the response.

I don’t personally have access to an Ubuntu machine but I can ask other community members.

We have worked around this issue for now by specifying Ubuntu-20.04 in the runner.

@MaksimZhukov
Copy link
Contributor

I am closing the issue since it is not related to GitHub hosted runners.
Feel free to contact us if you have any questions.

@mattyrob
Copy link
Author

@MaksimZhukov - Did you find that the process failed running on Ubuntu 22.04? How is it you are certain this issue is not linked to GitHub hosted runners?

If you can share the results and process of things you tried to reach that conclusion it may help me fix me issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: JavaScript and Node.js 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

5 participants