As of January 11, 2023 all my travis builds are failing. I tested the builds locally and they are not throwing any errors. I even re-ran a build that passed yesterday afternoon (1/10/2023) and now that build is also failing and throwing the same error as all recent builds from today. My git repo is clean, so this error makes no sense to me and it passes all tests locally. I believe the error is a product of the new deployed changes to Travis CI. The error I’m getting is:
I haven’t seen your .travis.yml but I’m assuming you’re using composer-merge-plugin, and I don’t recommend that unless you have a super specific need for it, not because it’s a bad project or anything but just because it can lead to so many unexpected edge cases like this.
Composer wasn’t built to have dependencies “sideloaded”, in turn you get weird outcomes like this. BLT used composer-merge-plugin up to version 10, and then removed it for these reasons. Maybe try downgrading the version of BLT you’re using.
I do see the log, but it’d be easier for me to parse through the original .travis.yml.
We just started seeing this today as well. In the past its been caused by source ${BLT_TRAVIS_DIR}/scripts/simulate_deploy. Im debugging right now but you can try removing that for now.
This takes the dirty state of your working directory — that is, your modified tracked files and staged changes — and saves it on a stack of unfinished changes that you can reapply at any time (even on a different branch), or try removing the Chromedriver license.