Travis API, requests stuck in `pending` state

Hey,

we use Travis API and some of our requests sporadically got stuck in pending state forever, those requests don’t differ in any parameters from others, the requests do trigger the build master branch. I wonder whether the problem is known to the community?

Example of the request (all private data is removed or masked by *, @ is replaced by #):

curl -s -X POST   -H "Content-Type: application/json"   -H "Accept: application/json"   -H "Travis-API-Version: 3"   -H "Authorization: token *"   -d'
{ 
  "request": {
    "branch": "master",
    "config": {
      "merge_mode": "deep_merge",
      "env": {
        "global": {
        *
        }
      }
    },
    "message": "Triggered by CURL command"
  }
}' https://api.travis-ci.com/repo/*/requests

Here is an example of the status check:

curl -s -X GET -H “Content-Type: application/json” -H “Accept: application/json” -H “Travis-API-Version: 3” -H “Authorization: token " https://api.travis-ci.com/repo//request/*
{
#type”: “request”,
#href”: “/repo//request/”,
#representation”: “standard”,
“id”: ,
“state”: “pending”,
“result”: null,
“message”: null,
“pull_request_mergeable”: null,
“repository”: {
#type”: “repository”,
#href”: "/repo/
”,
#representation”: “minimal”,
“id”: ,
“name”: "
",
“slug”: “/
},
“branch_name”: null,
“commit”: null,
“builds”: [

  ],
  "owner": {
    "#type": "organization",
    "#href": "/org/*",
    "#representation": "minimal",
    "id": *,
    "login": "*"
  },
  "created_at": "2019-12-09T17:49:47Z",
  "event_type": "api",
  "base_commit": null,
  "head_commit": null
}

Those requests are 100% syntax-correct as they duplicates of one another and most of them are successful. And in case of an error, the request should be rejected and not be stuck.

Thanks

Hi,
@egor-ryashin did you end up solving the problem? We have exactly the same issue. Without changing anything to our api calls that worked well, Travis is now reporting all new build requests as pending and the build never starts.

cheers

Nope, we’ve stopped using that API.

:smiley:
apparently it’s a server side issue atm. They are fixing it

thanks for your reply

Imprint