The symptom is that both "build" jobs succeed, but then all the "test" jobs fail with
$ STARR=$(sed -n 's/^maven\.version\.number=//p' buildcharacter.properties) && echo $STARR
sed: can't read buildcharacter.properties: No such file or directory
you can trace it back to the build job, where at the end it says:
store build cache
...
failed to upload cache
one hopes this is a transient problem at Travis-CI's end? since we didn't change anything
cc @dwijnand, who also noticed
you can trace it back to the build job, where at the end it says:
It's actually the workspace files, which aren't just an optimisation like the cache is:
Creating workspaces
Workspace: bootstrapped
0.00s1.67sadding /home/travis/build/scala/scala/buildcharacter.properties to workspace
adding /home/travis/.ivy2/local/org.scala-lang to workspace
adding /home/travis/build/scala/scala/target to workspace
adding /home/travis/build/scala/scala/project/target to workspace
adding /home/travis/build/scala/scala/project/project/target to workspace
adding /home/travis/build/scala/scala/project/project/project/target to workspace
adding /home/travis/build/scala/scala/dist to workspace
adding /home/travis/build/scala/scala/build to workspace
0.00s5.07schanges detected, packing new archive
uploading 215618203/bootstrapped.tgz
failed to upload workspace
maybe this is fixed now? https://github.com/scala/scala/pull/9477 passed
What an annoying problem, but it builds character. Which is why it's called buildcharacter.properties.
Looks like a bug in Travis-CI: https://travis-ci.community/t/repeatable-failed-to-upload-workspace-error/11108
haven't seen this lately
Most helpful comment
What an annoying problem, but it builds character. Which is why it's called
buildcharacter.properties.