unit tests do not clean after themselves

Bug #2070449 reported by Martin Kopec
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Fix Released
Undecided
Katarina Strenkova

Bug Description

After executing unit tests, there are 2 files left behind, one called None and the other resource_list.json

Steps to reproduce:
$ git clone https://opendev.org/openstack/tempest.git
$ cd tempest
$ tox-epy310
$ git status
On branch master
Your branch is up to date with 'origin/master'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
 None
 resource_list.json

Ideally, the files should be deleted after testing. Another issue is that if a user has a custom resource_list.json it will get overwritten by the unit tests.

Martin Kopec (mkopec)
Changed in tempest:
status: New → Confirmed
Martin Kopec (mkopec)
Changed in tempest:
assignee: nobody → Katarina Strenkova (kstrenko)
Changed in tempest:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.opendev.org/c/openstack/tempest/+/923293
Committed: https://opendev.org/openstack/tempest/commit/69f622b1085c23313c81db34e6b03193f28a6ac4
Submitter: "Zuul (22348)"
Branch: master

commit 69f622b1085c23313c81db34e6b03193f28a6ac4
Author: Katarina Strenkova <email address hidden>
Date: Tue Jul 2 14:14:39 2024 +0000

    Fix unit tests cleanup for --resource-list option

    This patch fixes the incomplete cleanup of unit tests for
    `record_resources()` function. These unit tests are tied with the
    tempest cleanup --resource-list option. The issue was the creation
    of None file and resource_list.json file while running unit tests.

    Closes-Bug: #2070449

    Change-Id: Id8ff96606b30d52ad4c8a6bd31bcb09ae03cc963

Changed in tempest:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tempest 40.0.0

This issue was fixed in the openstack/tempest 40.0.0 release.

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.