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

Stenciljs error end to end test

Pawan Singh
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!
Apr 18, 2023

MicrosoftTeams-image (13).png

When I ran end to end unit test for stencil.js I got this error in bitbucket pipeline. Local it's working properly. Tried multiple way to fix but not able to resolve. please help.

1 answer

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

Hi @Pawan Singh and welcome to the community.

Just to give you some context, Pipelines builds run in Docker containers. For every step of your build, a Docker container starts (the build container) using the image you have specified in your bitbucket-pipelines.yml file. If you use a service for a step, then a second Docker container will start for the service which will share a network adapter with your build container. The repo is cloned in the build container, and then the commands of the step's script are executed. When the step finishes these Docker containers get destroyed.

The Docker container where the build is running is a different environment than your local one. You also have a different environment if you use a different Docker image in your bitbucket-pipelines.yml file, as different images have different tools installed.

We have a guide for debugging pipelines builds locally with Docker:

I would suggest following this guide to debug your build locally and see if the issue is reproducible. When debugging locally, please make sure that you use the same Docker images as in your bitbucket-pipelines.yml file instead of the ones mentioned in the guide.

If the issue is reproducible locally, then the error is not specific to Pipelines (it may be related to the Docker image of the build container or your source code). When debugging locally, you can also run additional commands to troubleshoot this further. You could also try debugging it locally with different Docker images.

If you have any questions, please feel free to let me know.

Kind regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events