mahara-contributors team mailing list archive

[Aaron Wells <1515794@xxxxxxxxxxxxxxxxxx>]

Hm, actually it's failing trying to create a table. The
blocktype_taggedposts_tags, from artefact.blog/blocktype:taggedposts

This particular blocktype is the *only* blocktype that lives inside an
artefact *and* has its own install.xml file. So probably the deal is
that phpunit's tearer-downer isn't noticing that install.xml file
because of its unique location.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1515794

Title:
  phpunit database teardown is incomplete

Status in Mahara:
  Confirmed

Bug description:
  As noticed in Bug 1515473.

  If you run the Mahara phpunit tests twice against the same database
  (by doing "make phpunit") you get errors on the second run. Phpunit
  attempts to tear down the test database and re-create it, but it
  misses some items and errors out when it tries to recreate them,
  because they already exist. This happens in Postgres or MySQL.

  I'm guessing it's because there are some database entities that we
  create through direct execution of DDL statements rather than through
  XMLDB and install.xml files. Probably the teardown uses the
  install.xml files to remove everything, misses the directly-created
  things, and then the subsequent installer tries to re-create them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1515794/+subscriptions