do NOT reset DB in taler-bank-manage-testing, not healthy for auditor test

This commit is contained in:
Christian Grothoff 2019-12-23 12:32:37 +01:00
parent a3b56975a4
commit 8d51dd18ed
No known key found for this signature in database
GPG Key ID: 939E6BE1E29FC3CC
2 changed files with 1 additions and 5 deletions

View File

@ -10,8 +10,7 @@
set -eu set -eu
# Reset database, provide starting accounts # Ensure starting accounts exist
taler-bank-manage -c $1 --with-db $2 django flush --no-input
taler-bank-manage -c $1 --with-db $2 django provide_accounts taler-bank-manage -c $1 --with-db $2 django provide_accounts
# This is 'x' hashed by Django # This is 'x' hashed by Django

View File

@ -243,9 +243,6 @@ TALER_TESTING_run_bank (const char *config_filename,
* Prepare the bank execution. Check if the port is available * Prepare the bank execution. Check if the port is available
* and reset database. * and reset database.
* *
* NOTE: resetting the database is now done by taler-bank-manage-testing
* and should be removed here (once it works...)! FIXME!
*
* @param config_filename configuration file name. * @param config_filename configuration file name.
* *
* @return the base url, or NULL upon errors. Must be freed * @return the base url, or NULL upon errors. Must be freed