Job timeout configuration and plan-tier hard limits

Answer

The plan‑tier hard limit always overrides a user‑defined timeout value in .travis.yml. If the configured timeout exceeds the maximum allowed by your Travis CI plan, the job is terminated at the plan limit and the build is marked as a timeout failure (the same status used when the user timeout triggers).

Likely explanation

Travis CI enforces a ceiling on job duration that is tied to the subscription tier. The scheduler checks both the user‑specified timeout and the plan limit; the lower of the two values is the effective timeout. When the plan limit is lower, the job is killed by the system’s watchdog and the log shows a timeout‑related message.

Confirmed facts

• Travis CI documentation states that the plan‑tier maximum job length is a hard ceiling that cannot be exceeded by any timeout setting.
• When the limit is hit, the job receives a SIGTERM followed by SIGKILL if needed, and the build status is reported as "failed" with a timeout reason.

Steps needed for this case

1. Check your current .travis.yml for a timeout entry (value in minutes).
2. Determine the plan‑tier maximum job duration for your account (Free, Open Source, or a paid tier). This information is available in the Travis CI billing/usage page or the plan documentation.
3. If the user timeout is higher than the plan limit, lower it to the plan limit or remove the setting to let the default apply.
4. Commit the change and trigger a new build; verify in the job log that the timeout message references the plan limit (e.g., "Job cancelled due to exceeding plan timeout").
5. If you need a longer runtime than the plan allows, consider upgrading your Travis CI plan or using self‑hosted workers where the limit may differ.

To give a precise numeric limit, please confirm which Travis CI plan tier you are on (Free, Open Source, or a specific paid tier).