It sounds good to increase the limit, but I wonder if there is any low-hanging
fruit for reducing the job time. Are there any obvious tests that we could make
shorter without compromising the quality of test case? It might be worth having
a quick look for test cases that are taking too long.
Th
Sounds good to me
On Feb 24, 2015 6:27 PM, "Hongchao Deng" wrote:
> For the trunk, a successful test job takes ~1 hour . The current Jenkins
> config will abort the jobs if it takes more than 75 minutes.
> It would be super great to increase the limit:1. It might take more for a
> failed one, wh
For the trunk, a successful test job takes ~1 hour . The current Jenkins config
will abort the jobs if it takes more than 75 minutes.
It would be super great to increase the limit:1. It might take more for a
failed one, whose logs would be nice to view if not aborted.2. machine quality
might va
