import vmtest should not create dirs or initialize log

Bug #1594465 reported by Scott Moser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
Confirmed
Low
Unassigned

Bug Description

when working with a merge to add image information, i found/remembered that simply importing vmtest ends up writing some output to the console and creating a tempdir and a log.

Kind of obnoxious. Would be better if it did not.

Example:
$ python3 -m tests.vmtests.image_sync query --max=1 /srv/images/ release=precise
2016-06-20 17:15:37,765 - tests.vmtests - INFO - Logfile: /tmp/vmtest-2016-06-20T171537.765169.log . Working dir: /tmp/vmtest-2016-06-20T171537.765169
precise amd64/hwe-p 20160610.1 boot-initrd
precise amd64/hwe-p 20160610.1 boot-kernel
precise amd64/hwe-p 20160610.1 root-image.gz

Scott Moser (smoser)
Changed in curtin:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Scott Moser (smoser) wrote :

fyi, if we fix this might want to fix tools/jenkins-runner to use
   python3 -m tests/vmtests/image_sync
rather than
   PYTHONPATH=$PWD python3 -m tests/vmtests/image_sync.py

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.