Unable to run tests due to charm-proof 'failure'

Bug #1391088 reported by Stuart Bishop
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charmtester
New
Undecided
Unassigned

Bug Description

Attempting to run my charm's tests, it seems that bundletester wants to run charm-proof first. This will will always generate a warning, as my working directory does not match my charm name. It seems that this warning aborts the run, and no subsequent tests are run (I have 4, and bundletester seems to have another 5 to run after charm-proof).

stub@belch:~/charms/postgresql/enable-integration-tests$ bundletester -t `pwd` -l DEBUG
DEBUG:root:Bootstrap environment: local
DEBUG:deployer.env:Connecting to environment...
DEBUG:deployer.env:Connected to environment
DEBUG:deployer.env: Terminating machines
DEBUG:root:Waiting for services to be removed...
DEBUG:runner:call ['/usr/bin/charm-proof']
DEBUG:runner:
W: metadata name (postgresql) must match directory name (enable-integration-tests) exactly for local deployment.
I: Categories are being deprecated in favor of tags. Please rename the "categories" field to "tags".
I: config.yaml: option os_tenant_name has no default value
I: config.yaml: option aws_access_key_id has no default value
I: config.yaml: option listen_port has no default value
I: config.yaml: option wal_e_storage_uri has no default value
I: config.yaml: option os_auth_url has no default value
I: config.yaml: option aws_secret_access_key has no default value
I: config.yaml: option wabs_account_name has no default value
I: config.yaml: option install_sources has no default value
I: config.yaml: option os_username has no default value
I: config.yaml: option os_password has no default value
I: config.yaml: option wabs_access_key has no default value
I: config.yaml: option install_keys has no default value
I: config.yaml: option version has no default value
I: config.yaml: option swiftwal_container_prefix has no default value
I: config.yaml: option swiftwal_backup_schedule has no default value

DEBUG:runner:Exit Code: 100
disable-integration-tests
    charm-proof FAIL

------------------------------------------------------------------------------
FAIL: disable-integration-tests::charm-proof
[/usr/bin/charm-proof exit 100]
W: metadata name (postgresql) must match directory name (enable-integration-tests) exactly for local deployment.
I: Categories are being deprecated in favor of tags. Please rename the "categories" field to "tags".
I: config.yaml: option os_tenant_name has no default value
I: config.yaml: option aws_access_key_id has no default value
I: config.yaml: option listen_port has no default value
I: config.yaml: option wal_e_storage_uri has no default value
I: config.yaml: option os_auth_url has no default value
I: config.yaml: option aws_secret_access_key has no default value
I: config.yaml: option wabs_account_name has no default value
I: config.yaml: option install_sources has no default value
I: config.yaml: option os_username has no default value
I: config.yaml: option os_password has no default value
I: config.yaml: option wabs_access_key has no default value
I: config.yaml: option install_keys has no default value
I: config.yaml: option version has no default value
I: config.yaml: option swiftwal_container_prefix has no default value
I: config.yaml: option swiftwal_backup_schedule has no default value

FAIL: 1 SKIP:5 Total: 6 (0.219567 sec)

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.