Travis CI jobs for apache hudi taking a long time to schedule

[nsivabalan]

In recent times, we are noticing travis jobs are not triggered for Pull requests in “Apache Hudi” project. Guess these are resource contention as apache has lot of projects.

https://travis-ci.com/github/apache/hudi/builds
Eg:
PRs:
https://travis-ci.com/github/apache/hudi/builds/220777042
https://travis-ci.com/github/apache/hudi/builds/220884662

asf-site branch: Travis CI - Test and Deploy with Confidence

Is there any work around for this in general? How does other larger projects cope up with large requests for CI builds?

-Sivabalan

[Montana]

Hey Sivabalan,

Has this resolved?

[native-api]

• Check More options → Requests to see if the build request has been received and accepted. It it has and the build hasn’t started yet, that’s indeed resource contention.

• In the left pane, you can see “Runnning (X/Y)” – these are running jobs vs all currently existing jobs (you can click on that to see the actual jobs). I reckon you can probably only see stats for the projects that you have access to here so only someone with an admin access to the organization can see the whole picture and find out if you’re consistently hitting your resource limits.

• On your other questions, see

Build not getting triggered

The apache organization is huge. It runs a lot of jobs (e.g., at the moment, https://travis-ci.org/apache/kylin/jobs/677237970 https://travis-ci.org/apache/flink/jobs/676955592). Your build will run in time. Please wait.

Travis PR check job stuck in job received for 3+ hours

Oracle is a huge organization and has a lot of jobs queued up for execution. At this very moment there are 68 jobs either running or waiting in the queue. If you would like to have an increased build capacity, we are happy to discuss the plans with you. Please send email to support@travis-ci.com.