Juju Charms Collection
postgresql package

Tests Fail Consistently

Bug #1384894 reported by Charles Butler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
postgresql (Juju Charms Collection)
Fix Released
High
Stuart Bishop

Bug Description

When reviewing the latest merge into PostGres charm a blocker was introduced with the tests as they weren't being helpful and warrant revisiting to satisfy our Infra and CI story.

https://code.launchpad.net/~stub/charms/precise/postgresql/integration/+merge/233666

The consistent failure was on the PG91 test suite.

Tags: auto-test

Related branches

lp:~stub/charms/precise/postgresql/enable-integration-tests
On hold for merging into lp:charms/postgresql
Review Queue (community): Needs Fixing (automated testing)
Adam Israel (community): Needs Fixing
charmers: Pending requested
Diff: 2264 lines (+509/-1039)
17 files modified
.bzrignore (+1/-0)
Makefile (+51/-34)
config.yaml (+65/-63)
hooks/helpers.py (+0/-199)
hooks/hooks.py (+15/-15)
hooks/test_hooks.py (+0/-1)
lib/juju-deployer-wrapper.py (+15/-0)
templates/postgresql.conf.tmpl (+10/-0)
test.py (+149/-354)
testing/README (+0/-36)
testing/amuletfixture.py (+200/-0)
testing/jujufixture.py (+0/-297)
tests/00-setup.sh (+0/-15)
tests/01-lint.sh (+0/-3)
tests/02-unit-tests.sh (+0/-3)
tests/03-basic-amulet.py (+0/-19)
tests/tests.yaml (+3/-0)
lp:charms/postgresql
Marco Ceppi (community): Needs Resubmitting
Richard Asbridge: Pending requested
Diff: 0 lines
Revision history for this message
Stuart Bishop (stub) wrote :

Flagging this as incomplete. I need to know the canonical way to invoke the tests, so I can get the tests running in that fashion. I believe this is bundletester, but I haven't had success using it nor the standard way of invoking it to run a charm's tests (rather than pointing it to a bundle).

Changed in postgresql (Juju Charms Collection):
status: New → Incomplete
Revision history for this message
Stuart Bishop (stub) wrote :

Process seems to be:

branch charm into a fresh, empty charm repository
set JUJU_REPOSITORY
bootstrap the default juju environment
change to the charm directory in the charm repository
run 'bundletester'

Changed in postgresql (Juju Charms Collection):
status: Incomplete → Triaged
Matt Bruzek (mbruzek)
tags: added: auto-test
Revision history for this message
Matt Bruzek (mbruzek) wrote :

In an effort to improve quality, we are testing all charms in an automated process.

According to the latest test results by charm http://reports.vapour.ws/charm-tests-by-charm this charm is failing automated testing.

The bundle tester runs the `make lint` and `make test` targets, as well as all the executables in the postgresql/tests directory.

The charm is failing for trusty and the latest output can be found here:

http://reports.vapour.ws/charm-tests/charm-bundle-test-10308-results

Please investigate the cause of these failures and fix the charm or the tests so the postgresql charm passes automated testing.

Revision history for this message
Antonio Rosales (arosales) wrote :

Note, it looks like @Stuart is already working on resolving automated charm testing results.

Stuart Bishop (stub)
Changed in postgresql (Juju Charms Collection):
status: Triaged → Fix Released
assignee: nobody → Stuart Bishop (stub)
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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