# S390x jobs are stuck in the received state for days

**URL:** <https://travis-ci.community/t/s390x-jobs-are-stuck-in-the-received-state-for-days/10581>\
**Category:** Multi CPU Architecture\
**Tags:** build-env\
**Created:** [November 16, 2020, 1:28am UTC](https://travis-ci.community/t/s390x-jobs-are-stuck-in-the-received-state-for-days/10581 "2020-11-16T01:28:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kiszk](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/kiszk/32/5556_2.png) [@kiszk](https://travis-ci.community/u/kiszk)\
**Post date:** [November 16, 2020, 1:28am UTC](https://travis-ci.community/t/s390x-jobs-are-stuck-in-the-received-state-for-days/10581/1 "2020-11-16T01:28:53Z")

</div>

As you can see at [https://travis-ci.com/github/apache/arrow/builds](https://travis-ci.com/github/apache/arrow/builds), more than 10 jobs are queued from the last Friday.  
Most of the jobs have not almost executed. A job might be processed very slowly (two or three days after submitted).

Would it be possible to look at and fix this issue?

---

<div class="post-metadata">

**Author:** ![kiszk](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/kiszk/32/5556_2.png) [@kiszk](https://travis-ci.community/u/kiszk)\
**Post date:** [November 17, 2020, 8:31am UTC](https://travis-ci.community/t/s390x-jobs-are-stuck-in-the-received-state-for-days/10581/2 "2020-11-17T08:31:15Z")

</div>

I realized that travisCi jobs on s390x for other repositories works well (no delay). The delay problem for the starting job seems to be only on arrow repository.  
Is there any way to resolve this issue?

> **[Travis CI - Test and Deploy Your Code with Confidence](https://travis-ci.org/github/apache/zookeeper/builds/743972625)**

  

> **[Travis CI - Test and Deploy Your Code with Confidence](https://travis-ci.org/github/onnx/onnx-mlir/jobs/744095291)**

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [November 18, 2020, 3:17am UTC](https://travis-ci.community/t/s390x-jobs-are-stuck-in-the-received-state-for-days/10581/3 "2020-11-18T03:17:10Z")

</div>

In this case, this looks like

> [@Travis PR check job stuck in job received for 3+ hours](https://travis-ci.community/t/travis-pr-check-job-stuck-in-job-received-for-3-hours/10102/2):
>
> 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](mailto:support@travis-ci.com).

---

<div class="post-metadata">

**Author:** ![kiszk](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/kiszk/32/5556_2.png) [@kiszk](https://travis-ci.community/u/kiszk)\
**Post date:** [November 18, 2020, 7:07am UTC](https://travis-ci.community/t/s390x-jobs-are-stuck-in-the-received-state-for-days/10581/4 "2020-11-18T07:07:01Z")

</div>

Thank you for your reply. This happened one month ago. Did Oracle have a lot of jobs in the queue again?

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [November 18, 2020, 9:32pm UTC](https://travis-ci.community/t/s390x-jobs-are-stuck-in-the-received-state-for-days/10581/5 "2020-11-18T21:32:03Z")

</div>

I also see that you’re building on [travis-ci.org](http://travis-ci.org), so this also looks like

> [@Builds hang in queued state](https://travis-ci.community/t/builds-hang-in-queued-state/10250/6):
>
> We are in the process of migrating workers from [travis-ci.org](http://travis-ci.org/) to [travis-ci.com](http://travis-ci.com/) in preparation to fully shut down .org (or rather, make it read-only) on December, 31st. Unfortunately, this might happen as a result — if we see a job stuck in a queue for more than 16 hours, we will review this on a case by case basis and possibly cancel the job to ensure resources are not being reduced across the platform. Here’s a FAQ to clear things up: [https://docs.travis-ci.com/user/migrate/open-source-reposi…](https://docs.travis-ci.com/user/migrate/open-source-repository-migration#frequently-asked-questions)
