Skip to content
This repository has been archived by the owner on Oct 30, 2024. It is now read-only.

Broken CI runner with upgrade to 0.6.5 #132

Closed
junderw opened this issue Jul 29, 2020 · 6 comments
Closed

Broken CI runner with upgrade to 0.6.5 #132

junderw opened this issue Jul 29, 2020 · 6 comments

Comments

@junderw
Copy link

junderw commented Jul 29, 2020

We recently started updating an internal library that depends on ^0.6.3 of this library, and our CI was throwing segfaults.

I tried changing it to 0.6.4 and it worked, then 0.6.5 threw the same segfault at the same part. (It's our internal test for a signing helper function for transactions)

I have temporarily fixed this issue by changing from ^0.6.3 to a specific version, but just thought I'd let you know about this issue. Reverting the change and publishing a 0.6.6 version would be appreciated. (This change should be put off until a major version bump)

Thank you.

@junderw
Copy link
Author

junderw commented Jul 29, 2020

(I am referring to #130 )

@alcuadrado
Copy link
Member

Hi @junderw. Thanks for reporting this.

Do you have a link to your ci failure? If not, can you provide more info about the environment it's running on and what the test is doing?

Thanks

@junderw
Copy link
Author

junderw commented Jul 29, 2020

Sorry... it is a private repository, so no link.

Additional info we found: it was only crashing on node:12.13.0-alpine but not node:12.13.0...

So perhaps the code used in 0.6.5 is relying on glibc? (googling the issue, it seems like random segfaults on alpine are usually caused by glibc not being there)

@alcuadrado
Copy link
Member

alcuadrado commented Jul 29, 2020

So perhaps the code used in 0.6.5 is relying on glibc?

Yes, that's also my suspicion. This was present in keccak and secp256k1 until a few days ago.

Can you confirm that you were using the latest versions of these libraries? Maybe you had an older package-lock.json/yarn.lock.

For more info:

@holgerd77
Copy link
Member

@junderw any update on this?

@junderw
Copy link
Author

junderw commented Aug 4, 2020

I'll go ahead and close this... it was probably a lockfile keeping a dependency from updating... but the funny thing was that it was working fine up until I updated a dependency that depended on this library...

Perhaps another dependency had one of those deps and the highest common version requirement between this library and the other library was a version with the issue not fixed yet...

Either way, we decided to switch to debian based image instead of alpine.

@junderw junderw closed this as completed Aug 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@alcuadrado @holgerd77 @junderw and others