Code Monkey home page Code Monkey logo

Comments (7)

RazTamir avatar RazTamir commented on June 24, 2024

Is this blocking only deployment?
I just managed to execute tier 1 without issues

from ocs-ci.

mbukatov avatar mbukatov commented on June 24, 2024

@RazTamir it happens during collecting phase, it will affect any tests. The problem is visible since merge of #104, which was merged just few hours ago.

Edit: as Petr points out below, if you specify at least tests directory, pytest will collect test cases only there and you won't hit this.

from ocs-ci.

petr-balogh avatar petr-balogh commented on June 24, 2024

@mbukatov I see you didn't defined the folder of tests in you command so pytest is taking the ./ as default I think so than it's trying to collect everything under the path. So I think that user have to define the ./tests folder when running pytest to provide the path of tests where we have our tests.

So if you will run
py.test -m deployment --cluster-name mbukatov-ocsqe ./tests do you still see the issue?

from ocs-ci.

mbukatov avatar mbukatov commented on June 24, 2024

@mbukatov I see you didn't defined the folder of tests in you command so pytest is taking the ./ as default I think so than it's trying to collect everything under the path. So I think that user have to define the ./tests folder when running pytest to provide the path of tests where we have our tests.

You are right that pytest is trying to collect everything in the current directory. That said, making boundaries between unittests and actual tests explicit is a good idea, and I just forgot to make sure it's enforced.

from ocs-ci.

petr-balogh avatar petr-balogh commented on June 24, 2024

@mbukatov what do you propose to fix this? I see that boundaries are already defined in different folders which we documented should be used to run with. I think that it's normal from user to have specified test directory/path to be defined.

from ocs-ci.

mbukatov avatar mbukatov commented on June 24, 2024

@mbukatov what do you propose to fix this?

#109

I see that boundaries are already defined in different folders which we documented should be used to run with. I think that it's normal from user to have specified test directory/path to be defined.

Correct. It will just make pytest more resilient to such errors, esp. for deployment.

from ocs-ci.

mbukatov avatar mbukatov commented on June 24, 2024

Fixed by #109

from ocs-ci.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.