Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Test pipeline failed

billy August 7, 2023


My test pipeline suddenly started failing without any apparent changes, and it has continued to fail since then. The pipeline previously succeeded with the same commit, but now it's failing during execution. Is there something that might be wrong or updated in the Bitbucket pipeline recently?


It also happened last month but got resolved after i upgrade my plan to standard, but now it getting the same error vs last month. mostly error just


Uncaught UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#<Object>".


But this error is unlikely to happen and i never got this even with the same commit and configuration before or when i ran the same test on my local machine


Here's the test script I have in my Bitbucket pipeline:


image: node:16.17.0




image: mysql:5.7.17




memory: 6144


memory: 3072


- step: &TestScript

size: 2x

name: Test


- node


- apt-get update && apt-get install -y default-mysql-client

- mysql -h -u root -p[hidden] -e 'SET GLOBAL sql_mode=(SELECT REPLACE(@@sql_mode,"ONLY_FULL_GROUP_BY",""));'

- npm install

- npm run db:test:sync

- npm run db:test:seed

- npm test


- mysql

Is there any assistance or insights regarding the issues I'm encountering with this setup?

2 answers

0 votes
Hexmage August 11, 2023

Recently I've been noticing that my pipelines started building Node 18 while I specified lower versions (12 or 14 in my case) in my image. This might also be happening to you. Maybe try echoing the node version in the pipeline. I do have to say that I haven't resolved my own issue with this yet.

0 votes
Saxea _Flowie_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 7, 2023

@billy I'd say it's very unlikely to be related to Bitbucket the pipelines. In my experience this is usually a unnoticed difference in the environment configs or code behaving differently/unexpectedly; or just the fact that is running in a different environment which triggers a bug - quite often a race condition.

Perhaps you could try to handle the UnhandledPromiseRejection and JSON.stringify the object, which could give you more info about this issue?

billy August 7, 2023

hi @Saxea _Flowie_ thanks for replying 

It's been quite frustrating scouring for changes over the past few weeks. Given that I'm the sole contributor to this repository, it's rather perplexing that out of the blue, the pipeline failed even though the same commit had sailed through just yesterday.

The testing environment operates within containers and is completely isolated. Everything takes place on the Bitbucket pipeline server.

Interestingly, I encountered a similar hiccup last month that consumed days of my time in attempts to troubleshoot. Oddly enough, the problem mysteriously vanished on its own right after I decided to upgrade my plan.🤷‍♂️

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events