Travis fails to cache with ruby errors

I noticed recently that my builds took much longer than before due to lack of caching. I see the ruby error from travis at the end of my builds [1]:

/home/travis/.rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/uri/rfc3986_parser.rb:66:in `split': bad URI(is not URI?): https://travis-cache-production-org-gce.storage.googleapis.com/57856585/proof-kinding-fn/cache-linux-trusty-42fda5fc2ceff37d7208c6413dd4186a008e4cc9251052b5714f26b1ff2ba86e--compiler-: #GHC 8.4.3.tgz?Expires=1540439421&GoogleAccessId=GOOGZFGMULTAVLI3C63H&Signature=AoA8mU2jggQj320reS4Emii%2B7k0%3D (URI::InvalidURIError)
    	from /home/travis/.rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/uri/common.rb:188:in `split'
    	from /home/travis/.casher/bin/casher:217:in `path_ext'
    	from /home/travis/.casher/bin/casher:133:in `push'
    	from /home/travis/.casher/bin/casher:53:in `block in run'
    	from /home/travis/.rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/timeout.rb:88:in `block in timeout'
    	from /home/travis/.rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/timeout.rb:32:in `block in catch'
    	from /home/travis/.rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/timeout.rb:32:in `catch'
    	from /home/travis/.rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/timeout.rb:32:in `catch'
    	from /home/travis/.rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/timeout.rb:103:in `timeout'
    	from /home/travis/.casher/bin/casher:53:in `run'
    	from /home/travis/.casher/bin/casher:263:in `<main>'

Nothing has been changed in the travis configuration I have. This problem seems have stopped cache from being created and used. Is it a bug in travis?

Thanks in advance for any hints.

Zilin

[1] https://travis-ci.org/NICTA/cogent/jobs/445954673

Your compiler value (e.g., https://github.com/NICTA/cogent/blob/34a9ff06c943b48ec03406e1fa8bba4033405925/.travis.yml#L39) contains spaces and an octothorp, and therefore incorrect for the purpose of calculating cache name and its URL.

Ah, thanks heaps for the hint. Just ooc, I presume there was something changed behind the scene as the url hadn’t been a problem before. So in general where shall I be looking for these (incompatible) changes from the travis-ci side in future?

Thanks for that information. https://github.com/travis-ci/travis-build/pull/1015 was merged and deployed on October 24, when the first error was observed.

We’ll take a look at it soon.