Up until about a year ago, the Linux shared objects (SOs) were automatically committed to the Git repository by Travis after any change that affected them. This is no longer happening.
For instance, the commit dc4189a triggered automatic commits of libbulletjme.dylib and bulletjme.dll (both 32-bit and 64-bit) but failed to update libbulletjme.so (either version). libbulletjme.so hasn't been updated since e12261e back in August 2017.
Travis job 2286.1 completely successfully. It executed private/upload_native.sh, and the outcome was nothing to commit, working directory clean.
I'm unsure where to go from here.
Up until about a year ago, the Linux shared objects (SOs) were automatically committed to the Git repository by Travis after any change that affected them. This is no longer happening.
For instance, the commit dc4189a triggered automatic commits of
libbulletjme.dylibandbulletjme.dll(both 32-bit and 64-bit) but failed to updatelibbulletjme.so(either version).libbulletjme.sohasn't been updated since e12261e back in August 2017.Travis job 2286.1 completely successfully. It executed
private/upload_native.sh, and the outcome wasnothing to commit, working directory clean.I'm unsure where to go from here.