nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

problem with a long running python unit test

tomeks86

I have a problem with a failing python unit test in the bitbucket pipeline. The test is a long running one - almost 1.5 s locally and with assertions checking files on the disk. It passes both locally and in the locally run docker container.

In the logs I found that it first checks the assertions and then the tested method writes the files. Is there any implicit asynchronicity in the bitbucket pipelines?

Thank you in advance for your expertise,

Tomasz

Accepted answers

Philip Hodder

Hi Tomasz,

Can you include some more information about the failing unit test? What's the error, and what is it testing? Is it doing any multithreaded operations? (As we've found this is often a source of inconsistencies in results.)

The build script itself runs synchronously.

Thanks,

Phil

All comments

Philip Hodder

Hi Tomasz,

The build script itself runs synchronously.

Thanks,

Phil

tomeks86

Hello Phil,

I re-enabled the failing test and you can find the log with the failing test here:
https://bitbucket.org/tomeks86/chi1chi2/addon/pipelines/home#!/results/86

There are no multithreaded operations involved, at least to my knowledge.

I'll be glad if you can find an answer,

Tomasz

Philip Hodder

Hmmmm. Tricky...

Try the following config, lets see if the files actually get created after the tests finish.

image: tomeks86/python-openbabel

pipelines:
  default:
    - step:
        caches:
          - pip
        script:
          - pip install -r requirements_test.txt
          - flake8 --ignore E501,E126 chi1chi2/
          - python -m unittest discover tests/
        after-script:
          - ps # Check to see if python processes are still running.
          - ls -R # Lists all files. Check to see if necessary tests files are actually created.

I've added an after-script. Which will always run after you main script completes (regardless of if it succeeds or fails).

tomeks86

I tried it:

https://bitbucket.org/tomeks86/chi1chi2/addon/pipelines/home#!/results/95

as well as listing the /tmp directory in the build step:

https://bitbucket.org/tomeks86/chi1chi2/addon/pipelines/home#!/results/96

Nothing interesting unfortunately...

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

bitbucket-pipelines