Odd error in one repo, works in another

Travis CI Discussions & Feedback
1

I’m getting a rather unhelpful error message from Travis:

There was an error in the .travis.yml file from which we could not recover.

Unfortunately, we do not know much about this error.

Please review https://docs.travis-ci.com, or contact us at support@travis-ci.com with the error ID: a8a8adb30b6c4a65a2d4442534584721

The parser on config.travis-ci.org seems to deal with the file just fine, but the really weird thing is that I tested the same commit (as in the commit IDs match) in a different repository and it works perfectly.

2

Have you tried running the build in debug mode to see if you can get a more detailed error?

-Montana

3

It’s a bug on our code. I’ll take a look soon.

4

OK. I’ve dug this a little deeper, and found the following. It’s not a bug, per se.

The problem here is that your configuration does not conform to the documented shape.

It should look like:

    addons:
      apt:
        sources:
          - sourceline: 'deb http://apt.llvm.org/bionic/ llvm-toolchain-bionic-9 main'
            key_url: 'https://apt.llvm.org/llvm-snapshot.gpg.key'
        packages:
        - clang-9

Notice that addons.apt.sources is an array, not a hash/map, which is what you have in, e.g.,

It works in one of the repositories because that one has the configuration validator enabled, and it normalizes your configuration into something that we can use (see


for more information on this subject.), while the other does not use the validator, and it results in an error.

You should either fix your configuration, or enable the validator on the failing repo.

5

Ah, that makes sense! I’ll fix my repo and enable the validator.

It would be nice to have a better error message, but yeah that was a dumb mistake on my end. Sorry for the noise, but thank you very much for looking into this and explaining the problem.

Way off-topic: your name on here still says you’re on vacation until January 6.

6

For a small class of configuration errors, we do. Other errors we have not seen, we unfortunately cannot. The validator will help us deal with this a little better.

1 Like