Switch network-checker to testrepository

Bug #1516625 reported by Andrey Tykhonov
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel Sustaining
Mitaka
Won't Fix
Medium
Fuel Python (Deprecated)
Newton
Confirmed
Medium
Fuel Sustaining

Bug Description

Nova, neutron, and keystone are three OpenStack projects that currently use testr (are already migrated to testrepository). network-checker needs to be migrated as well.

Revision history for this message
Sebastian Kalinowski (prmtl) wrote :

Hold your horses, mate.

Solar team developed an addon that enables testrepository in pytest. Talk with Lukasz Oles about it.

This bug is invalid.

Changed in fuel:
status: New → Invalid
Revision history for this message
Roman Prykhodchenko (romcheg) wrote :

It was already discussed a dozen of times. We should not invent our own wheels. Pytest will never be added to openstack ecosystem while there is another test manager there.

Changed in fuel:
status: Invalid → Confirmed
assignee: nobody → Fuel Python Team (fuel-python)
milestone: none → 8.0
Revision history for this message
Roman Prykhodchenko (romcheg) wrote :

We successfully used testr in python-fuelclient. It works and no one dies as the result.

Revision history for this message
Thomas Goirand (thomas-goirand) wrote :

Hi. Please don't waste everyone's time, and do what's needed. The package *must* switch to testr so that it complies with OpenStack standard. You are free to use another test runner locally if you wish, but testr is the standard for the gate, and we are not allowed to change that. See Monty's reaction on the openstack-dev list about it.

summary: - Migrate network-checker to testrepository
+ Switch network-checker to testrepository
Revision history for this message
Sergii Golovatiuk (sgolovatiuk) wrote :

Bug is valid. To be a BigTent project network-checker MUST meet openstack standards.

Revision history for this message
Jay Pipes (jaypipes) wrote :

Yes, folks, please do switch to using testr for the network-checker test manager. It's a requirement for the Project Test Infrastructure upstream. It's not a nice to have :)

Revision history for this message
Sebastian Kalinowski (prmtl) wrote :

This is nuts. Do you even know about what am I talking about? Did you even checked that plugin I'm talking about? I am 100% sure that no one of you even talked to Łukasz.

@Roman,

> We successfully used testr in python-fuelclient. It works and no one dies as the result.

Don't lie. There were at least two bugs BECAUSE of using testr which you were asking me to help you with.

@Thomas,

> Please don't waste everyone's time, and do what's needed.

Oh, this is very nice. I want to remind you that I'm still waiting for a technical reasons from you for not using py.test ;)

description: updated
Revision history for this message
Tomasz 'Zen' Napierala (tzn) wrote :

Bug is still valid, it's a requirement for every project to be able to launch tests with testr. However pytest plugin for testr might solve this issue, but needs some discussions.

Revision history for this message
Roman Prykhodchenko (romcheg) wrote :

Sebastian, the only technical reason for that is that OpenStack CI relies to subunit to perform some operations. The non technical reason is that running tests with testr is a requirement. I don't see any reason to use any other framework, if we can go with just one. Saying that I oppose using testrepository together with pytest or any other "our" framework which is not accepted in the upstream.

Open source is not about conversations de couloir, it's about open facts here and now. No one has to go to anyone to ask why this bug is invalid. It has to be here.

No, I didn't lie saying no one died because of switching to testr. Those two bugs were related to already known issues and can be easily avoided. The rest of OpenStack project teams is still alive by the way, as well.

Dmitry Pyzhov (dpyzhov)
tags: added: tech-debt
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

Moving medium bug to 9.0 because we have SCF in action for 8.0

Changed in fuel:
milestone: 8.0 → 9.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.