-
Notifications
You must be signed in to change notification settings - Fork 53
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 Actions stuck at "Warning: vkCreateInstance: Found no drivers!" #115
Comments
I think this is another instance of the bug caused by Chrome updating their headless configuration: quarto-dev/quarto-cli#10626 By default, our actions install the latest stable version of Quarto, which currently has this issue. We fixed this bug in the 1.6 prereleases, but the 1.5 patch release happens once a month, and so will (hopefully) be fixed on Sep 1 with 1.5.57. You can try to render with the prereleases by configuring the setup action like so: - uses: quarto-dev/quarto-actions/setup@v2
with:
version: pre-release Of course, this will mean you're now rendering with 1.6 instead of 1.5. But it should be enough for you to check that the issue is resolved. |
Our repo is having a similar breakdown upon build. The issue also seemed to stem from the render workflow Hope this helps.
|
We decided to go ahead and create a new stable 1.5 release ahead of schedule because of these reports. If you can confirm that your CI is using 1.5.57, then this issue should be fixed. |
Here's a link to the working build with the manual PDF render: https://github.com/ianalexmac/aetr-web-book-2024/actions/runs/10620510306/job/29440437978 It appears to be using CI 1.5.57 |
Ok, thanks. I'm going to go ahead and close this issue, then. |
Thank you! |
Hmm, my GitHub Action is using the latest stable version of Quarto (1.5.57), and it is still running into the same issue. Any ideas? |
@isaactpetersen You're correct, there's an additional issue in the setup stage. @cderv is investigating a fix (we have the same problem in quarto-web) and we'll let you know more when we do. |
The only way we know how to partially work around this problem (which is unfortunately not a Quarto problem, as you can see by the place where your CI hangs) is to disable Chromium installation and usage entirely in CI. This is very unfortunate because you will not be able to render documents that (for example) have |
You can try the change we made on |
Thanks for the prompt responses. I appreciate it. Will this be fixed with the patch release on 9/1, or will I need to make the change you indicated for the forseeable future, in order to get my quarto website to render? |
I have made a new v2.1.6 release with opting out the chrome checking that creates the problem. v2 and v2.1 tag are updated too. Using This means that could happen again, but we'll find a new solution that don't create problem on CI. |
I don't know if this is the right place to post this question, but I'm having an issue with rendering my Quarto website via GitHub Actions, and I'd appreciate help in either solving the issue or in finding the right place to post this question. My GitHub Action recently has been getting stuck on a particular step--the workflow had worked fine in prior runs, so I'm not sure what happened.
Here is my failing workflow: https://github.com/isaactpetersen/Fantasy-Football-Analytics-Textbook/actions/runs/10605075217/job/29393117856
The Action gets stuck on the job "Render Quarto Project":
My workflow file is below:
I'm not sure why I'm getting these warnings (and why the Action gets stuck), and my Action used to run fine. Any guidance would be greatly appreciated. Thanks in advance!
The text was updated successfully, but these errors were encountered: