For the past week, travis jobs submitted from Github for our eclipse/scanning 
project have been incredibly slow to get a slot.

It used to be the case that they would start within a few minutes before early 
afternoon in the UK, but take up to an hour late in the afternoon, but recently 
it has been frustratingly long as early as 9am, including waits of 8 to 10 
hours for a 13 minute job to be initiated.

After they tweeted that their Linux Open Source backlog was cleared, I 
contacted travis support and was told:

I'm seeing that the queue in which your jobs were waiting were most likely 
waiting behind other jobs in the "eclipse" github organization. If this wait 
time is a recent development for you, it may be because of another project or 
projects in the "eclipse" organization triggering an unusually high number of 
jobs. We typically advise folks who manage large organizations to take 
advantage of the per-repository concurrent build limits 
https://docs.travis-ci.com/user/customizing-the-build/#Limiting-Concurrent-Builds.
 I hope that this helps!

Is there any guidance on the number of concurrent builds we should be trying to 
stick to? Is there any monitoring of whether were are exceeding these limits 
and taking more than our fair share of the available job slots? Is there 
anything that we can do to get our builds to run more promptly, other than pull 
this testing in-house?
Since the delays started growing, I've switched from "only do eclipse work in 
the morning and iterate quickly on one thing at once" to "start multiple 
parallel things at once, queue them all up and check on their progress the next 
day", sadly if everyone did this it would just make matters worse.

Your thoughts and advice would be appreciated.


Mark..........

-- 
This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

_______________________________________________
incubation mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation

Reply via email to