In the past few days, Travis has started ignoring apt packages that I’m installing via the config. This is causing builds to fail (and Travis is a lot less useful now!).
I don’t think I’ve changed anything that might cause this change.
If you could find a reference of what the official YAML spec says the parse result should be in such a case, we can rule if this is a bug or not. Travis adheres to YAML 1.1.
I did run the config through some YAML validators, which it passed fine. However, I did some research and found that keys must be unique in YAML, so the duplicate ‘addon’ keys do make it invalid- even though validators don’t seem to catch that.
This solves the problem for me; I would consider it a bug that Travis doesn’t reject invalid input.