So, I have been getting these flaky errors on CI a...
# javascript
a
So, I have been getting these flaky errors on CI alot.
Copy code
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':kotlinStorePackageLock'.
> Lock file was changed. Run the `kotlinUpgradePackageLock` task to actualize lock file
How do you solve this?? Am I not checking some files into VCS??. I am calling them flaky because the errors do not show when you rerun the workflow
e
Ha! Same issue as mine months ago. Never understood what happened. I've set the check to WARNING instead of ERROR for a while in CI, then reverted it.
This was my commit's content
Copy code
// May be dangerous for unexpected transitive dependencies
// TODO: understand what is going in with yarn.lock.
//  Why is it complaining on Jenkins even tho we have
//  committed the changed yarn.lock?
yarn.yarnLockMismatchReport = YarnLockMismatchReport.WARNING
a
@PHondogo But I do need
package.lock
(I am no longer using yarn) to throw an error if there are changes in the downloaded dependencies. So, disabling it will defeat the purpose. No??? Question is, why is it failing and then passes (either on 1st or 2nd retry)?
e
a
I was just going through the issues. and I have taken an interest in KT-70902. Now, it really not my issue but it is highly related to it. Perhaps when its resolved, all will be well
a
The package lock stuff bugs me too. I've been thinking about how to resolve it, and I read that
npm ci
is more consistent and reproducible than
npm install
. Maybe Kotlin/JS should use
npm ci
instead? (I'm a JS dev noob so I'm just thinking out loud, and wonder what you more knowledgable people think.)