-
Notifications
You must be signed in to change notification settings - Fork 41
Conversation
Sounds like a good idea, but I think that we may want to put information about timeout somewhere (maybe in readme with link to github docs?) |
add information on CI timeout to README.md
Maybe 30 minutes is a bit tight looking at the results from the last run. Should we choose 45 or 60? |
Ok. I think wrongly understood you initially. I think that you want to set timeout in Because this workflow file is used in template output. Or you have a problem with running tests of this repository? |
Sorry, my mistake. You initially got it right, but I obviously modified the wrong file. |
this avoids using large amounts of CI time when playing with a plugin draft.
Any idea what is going on here? Looks like a git problem when setting up the plugin. |
Hmm @martinschorb I think what's happening is that the workflow file has lost its newline at the end of the file, so the pre-commit that runs on the built plugin fails. You should be able to fix it by adding a newline back to the end of |
Actually, I think it's the opposite: a newline has been added at the end of I tried to do the modification myself, but I couldn't push the changes to this PR. Maybe @martinschorb or @Czaki can do it. |
{{cookiecutter.plugin_name}}/.github/workflows/test_and_deploy.yml
Outdated
Show resolved
Hide resolved
I went through the test logs and I think the problem comes from the end of the generated `test_and_deploy.yml' file, pre-commit fails with the "fix end of files" hook. I think the cookiecutter is producing an excess new line:
|
When playing around with a repository created from this template, a GUI test ended up in an infinite loop.
The default timeout of 6h and the 3x3 matrix to test different OSes and Python version then leads to a quick exhaustion of the time available for Github actions.
Since this repo is directed to beginners, I assume this can happen more often, so I propose a shorter timeout to minimize such problems.
Thanks!