Github plugin reports build is queued (forever) if .travis.yml contains parsing error

Travis CI Discussions & Feedback
1

Here is my .travis.yml file:

dist: bionic
sudo: false
# Avoid re-downloading dependencies on every build
cache:
  yarn
  directories:
    - "$HOME/.m2/repository"
services:
  - docker
script:
  - cp .travis/settings.xml $HOME/.m2/settings.xml
  - ./mvnw --batch-mode --show-version install
branches:
  only:
    - master

The parsing error is caused by cache containing multiple entries that are not prefixed by a hyphen. When I view my job on https://travis-ci.com/ (requests tab) I see Could not parse [job id] but when I go on my Github pull request, “checks” tab I see a “Queued X minutes ago”.

Expected behavior: Github plugin should report that the yml file cannot be parsed, instead of reporting the build is queued forever.

2

Hello, there. Which repository is this?

3

Hi Hiro,

It is a private commercial repository. Do you need any bits that I have not shared above?

Gili

4

In that case, please email support@travis-ci.com with details, and we’ll take a look.

5

+1

Same problem here, private repo.

We recently had a merge commit on GitHub that weirdly added some whitespaces to the .travis.yml. The branch was building fine before and for the malicious merge commit, GitHub stated “Expected - Waiting for status to be reported”. Within TravisCI, the merge commit was marked as built and failed because of the malformed .travis.yml, but the failing status never got reported to GitHub.