You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi! Recently I've got a very strange error during bitbucket pipelines execution:
2020-12-11T14:36:21.5200365Z stderr P
Pipelines worked fine, then they stopped working suddenly and started to return that weird message.
My configuration uses docker
image: docker/compose:1.25.4
options:
docker: true
definitions:
services:
docker:
memory: 3072
caches:
pipelines:
default:
- step:
name: Run Unit tests
script:
- apk add --no-cache git openssh
- git submodule update --init
- cp .env.example .env
- cp phpunit.xml.dist phpunit.xml
- cp /opt/atlassian/pipelines/agent/ssh/id_rsa .docker/node
- cp /opt/atlassian/pipelines/agent/ssh/id_rsa .docker/composer
- mkdir -p .docker/.storage/composer && chmod -R a+rw .docker/.storage/composer
- docker-compose build
- docker-compose run --rm composer install --no-progress
- docker-compose run --rm phpunit dockerize -wait tcp://mysql:3306 -wait tcp://mongodb:27017 -timeout 60s
- docker-compose run --rm phpunit ./artisan migrate --seed
- docker-compose run --rm phpunit vendor/bin/phpunit --configuration ./phpunit.xml --testsuite 'Checkout Unit'
- docker-compose run --rm phpunit vendor/bin/phpunit --configuration ./phpunit.xml --testsuite 'App Api'
- docker-compose run --rm phpunit vendor/bin/phpunit --configuration ./phpunit.xml --testsuite 'Checkout Api'
The first 2 testsuites work fine, pipeline is failing on the third testsuite and returns me
stderr P error that I see in docker-compose logs.
Tests work fine on my local machine, and they worked fine in bitbucket until recently.
Can anybody give me any clue what's wrong?
I checked if anything is spoiling stderr, nothing is logging there.
This happened to me when I tried to import a library called opencv for python, but I guess it could happen for any other language/library. For anyone checking this, try to see if any recent library added could be causing you troubles.
Anyway, looks like a bug, the error should be visible in the GUI
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.