please increase 30 minute timeout
As seen in https://ci.appveyor.com/project/GitMensch/gnucobol-3-x/builds/51829380/job/c2617ux0kd9pcihv the timeout is reached (sadly, not much time more would be needed).
Can you please extend https://ci.appveyor.com/project/GitMensch/gnucobol-trunk and https://ci.appveyor.com/project/GitMensch/gnucobol-3.x to 60 minutes?
Of course a way to get more CPUs would be much preferable, then the time wouldn't be an issue either, but it seems "free open source" is stuck on 2 threads, right? With the timeout increase this can be worked around.
Thank you,
Simon
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 05 Apr, 2025 04:01 AM
it should be 60 minutes already.
2 Posted by human on 04 Jun, 2025 05:52 AM
> it should be 60 minutes already.
We often do get timeouts at https://ci.appveyor.com/project/GitMensch/gnucobol-3-x on exactly 30 minutes - which is extremely inconvenient as the tests are normally done around 95% until then, so we end up retriggering the builds until it finally works (landing with 27-29 minutes then) :-/
Support Staff 3 Posted by Feodor Fitsner on 04 Jun, 2025 04:08 PM
Make sure you don't have build time limit configured on project level. For account it's currently set to 60 minutes.
Feodor Fitsner closed this discussion on 04 Aug, 2025 09:03 PM.