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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Build error: Cannot call constructor

Have been building without issue, and then this morning they spontaneously began to fail continuously fail with:

 Fatal error: Uncaught Error: Cannot call constructor in /opt/atlassian/pipelines/agent/build/vendor/symfony/finder/Comparator/DateComparator.php:48

2 answers

0 votes
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Feb 15, 2023

Hello @Jeff Greenberg 

Did you find the solution? I just found your question on Google.

I have the same issue with Magento instances on Jenkins. Different projects are failing randomly from time to time.

The strange thing, I was able to reproduce the issue a couple of times on my local, but XDebug did not stop on this line no matter I had a breakpoint there.


Thank you in advance if you have any information on this issue.

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 19, 2022

Hi Jeff,

The issue could be related to changes in your source code, dependencies, or the Docker image you use for your builds.

I would suggest debugging this locally with Docker first to figure out if that's the case. If the build fails with the same error locally, then the issue is most likely not related to Pipelines, and you can debug this locally without consuming Pipelines minutes.

You can find step-by-step instructions on how to debug this locally in my reply to another question here:

It's important to use a clone of the repo at the commit with the failed build, and also use the same Docker image that you use as a build container for the failed step.

Kind regards,

Hi. The non-pipeline possibilities as the issue might make sense if failure were consistent rather than my experience of 5 succeed, 1 fails, 2 succeed, 4 fail, etc. 

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 26, 2022

Hi Jeff,

You can create a ticket with the support team and provide the URL of some of the builds that fail and some of the ones that succeed, so we can look further into this issue. If there is a support ticket open, the engineer working on your case will be able to access the builds and additional logs in order to investigate.

You may still be asked to debug one of the failed builds locally, as that's usually the first step in determining if the issue is likely to be caused by pipelines or not.

You can create a ticket via, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product.

Kind regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events