Timeout 30 minutes reached, please restore to 60 Minutes

Simon Sobisch's Avatar

Simon Sobisch

15 Oct, 2025 10:09 AM

see https://ci.appveyor.com/project/GitMensch/gnucobol-trunk/builds/52898918
also happens on
https://ci.appveyor.com/project/GitMensch/gnucobol-3-x (but failed builds already deleted)<

These builds are still running their tests and are commonly around 80-95% when they hit the timeout.

Please restore the previous 60 Minute timeout for both environments, as the alternative "click 'rebuild failed' until it works with 28/29 minutes is definitely worse and takes both a manual approach and more resources for the workers as well.

Thank you,
Simon

  1. Support Staff 1 Posted by Feodor Fitsner on 16 Oct, 2025 04:40 PM

    Feodor Fitsner's Avatar

    Hi Simon,

    Account "GitMensch" has 60 minutes timeout. It could be a timeout set for that specific project - check your project config.

  2. 2 Posted by Simon Sobisch on 16 Oct, 2025 07:14 PM

    Simon Sobisch 's Avatar

    Ah, that's true. I've raised that to 60 and guess the issue is solved - thank you very much!

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

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