Hi!
I have an issue when I try to run the tests with firefox browser in Bitbucket Pipeline, the tests never finish and after 2 hours shows the error -> "Exceeded build time limit of 120 minutes", I don´t know why is happening that, because I´ve tried with Edge and Chrome browsers and they´re okay.
This issue has been happening for 5 days so I think it´s the last version of Firefox, because the previous time it was working. Also, I´ve tried with old versions but I´ve got the same problem.
Please, can you help me with that?
Thanks in advance.
Hey @Kimberling Yarihuaman ,
and welcome to the Community!
My understanding is that you have some tests implemented on your pipelines that test your code in different browsers, but for firefox specifically, it started to fail recently.
Would you mind elaborate on how you're executing these tests in pipelines? Are you using a service container in your pipelines step to emulate the browser, or using a different approach ?
If you feel comfortable in sharing here on community, it would greatly assist the investigation to see your YAML file. If you can share the particular step in YAML that is currently failing/stuck, it may help us to suggest possible next steps.
On a side note, I see you have access to a workspace with Premium subscription which is entitled to Premium support. If you'd like fast responses/turnaround, you can create a support ticket here providing the link of the Premium workspace you're member of.
Thank you, @Kimberling Yarihuaman !
Patrik S
Hi @Patrik S !
Thanks for your answer, so I´m using bitbucket-pipelines.yml file, I attached a screenshot about my steps in that file. I´m working with Cypress, Cucumber, Gherkin and Javascript to automate the tests.
I´am going to take into account the possibility to create a support ticket. In this case, should I provide the repository link of the Premium workspace? (sorry, but I don´t understand this part)
Thanks in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Kimberling Yarihuaman ,
Thanks for sharing the screenshot.
I'm not really familiar with cypress, but one thing I can think of is your step running close to the memory limit, and somehow causing the tests to get stuck hence resulting in the build to timeout.
For that, I would suggest trying increasing the step size to 2x, so it will get 8GB of memory (compared to 4GB by default):
- step:
name: Install dependencies and run tests in Firefox
size: 2x
script:
- <your script commands>
If that doesn't work, you may want to try troubleshooting the pipeline locally to see if the same error happens and isolate if it only happens on the pipelines environment, or in your local environment as well:
Thank you, @Kimberling Yarihuaman !
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're very welcome @Kimberling Yarihuaman !
Happy to hear that increasing the memory did the trick :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah! @Patrik S I have a question. Why could it be happening that? Because it´s working with size: 4x.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.