Commit 1674224
committed
[Build] Specify timeout for test execution after agent was accessed
The top-level timeout specified in the global options of a Jenkins job
is effective from the time the job starts its execution (waiting for the
'main' agents is excluded here). On the contrary timeouts defined on
stage level include the time waiting for the stage's agent to become
available.
In some cases (currently only for Mac) the same physical machine is used
to execute multiple test-configurations. Consequently some
configurations have to wait a significant amount of time for the
executing agent to become available.
Therefore now timeouts are defined:
An inner one effective only for the actual test execution, sufficient to
execute one configuration.
And an outer, global one, effective almost from when the job is
triggered and with a larger value to cover the execution of multiple
configurations.
The global one mainly exists in order to prevent pending tests to pile
up in case the infrastructure is flawed.
Follow-up on
- eclipse-platform#34161 parent a5315fe commit 1674224
1 file changed
Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2 | 2 | | |
3 | 3 | | |
4 | 4 | | |
5 | | - | |
| 5 | + | |
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
| |||
48 | 48 | | |
49 | 49 | | |
50 | 50 | | |
51 | | - | |
| 51 | + | |
52 | 52 | | |
53 | 53 | | |
54 | 54 | | |
| |||
92 | 92 | | |
93 | 93 | | |
94 | 94 | | |
95 | | - | |
| 95 | + | |
96 | 96 | | |
97 | 97 | | |
98 | 98 | | |
| |||
0 commit comments