Pipeline failing on same build as last week

[osep_redmine]

I'm trying to re-run a build that was successfully run on February 4th, but it is failing when executing `npm install --include=dev`.

Build #780  ran successfully on Feb 4 for commit `a1f5fb3`.

Build #786 for the same commit is failing today with the error:

+ npm install --include=dev
Error relocating /usr/bin/node: sqlite3session_attach: symbol not found
Error relocating /usr/bin/node: sqlite3changeset_apply: symbol not found
Error relocating /usr/bin/node: sqlite3session_create: symbol not found
Error relocating /usr/bin/node: sqlite3session_changeset: symbol not found
Error relocating /usr/bin/node: sqlite3session_patchset: symbol not found
Error relocating /usr/bin/node: sqlite3session_delete: symbol not found

According to the `Build setup` step output, both runs use the same Docker image for the build (docker.io/library/composer@sha256:e0c9ac329256c25b0dee572df37d986570fb26bb6baaa7d0abe69b84181701e1)

Assistance required to resolve as we currently cannot deploy code.

[Ben]

Hi @osep_redmine 

If you are re-running the build that succeeded previously, and it is now failing - it could be something to do with the current state of your repository.

The symbol error you're receiving is typically related to dependencies, so running an apk upgrade prior to the npm command may solve it - I found an article on this below that may be helpful:

• https://github.com/nodejs/node/issues/41058

If this does not resolve the issue - I'd recommend adding debugging to your npm command to reveal further information about the root cause of the error:

• npm install --verbose --include=dev

Cheers!

- Ben (Bitbucket Cloud Support)

[osep_redmine]

It started working again. I think there was a transient BitBucket issue.