I came across this issue when running e2e tests after we had just released new asset versions. Inside the autoload folder inside the e2e directory it still has all the old assets and the current assets inside it. This ends up causing a fatal error running tests locally.
All the code in charge of managing the assets in the autoload folder are inside e2e/test/download-assets.js
When calling downloadAssets(), it should download all the latest assets first, then check the autoload to see if there are older or duplicate assets, and then delete the duplicates/older assets.
As of right now if I do not manually clear out my autoload folder a fatal error happens when running a test. This is my autoload contents when the error occurs:
I came across this issue when running e2e tests after we had just released new asset versions. Inside the
autoload
folder inside thee2e
directory it still has all the old assets and the current assets inside it. This ends up causing a fatal error running tests locally.All the code in charge of managing the assets in the
autoload
folder are insidee2e/test/download-assets.js
File: /teraslice/e2e/test/download-assets.js
When calling
downloadAssets()
, it should download all the latest assets first, then check the autoload to see if there are older or duplicate assets, and then delete the duplicates/older assets.As of right now if I do not manually clear out my autoload folder a fatal error happens when running a test. This is my autoload contents when the error occurs:
Then when running
yarn test:elasticsearch7
inside the e2e directory I see this in my teraslice master logs container: