gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: add section "Manual Testing Database


From: gnunet
Subject: [taler-docs] branch master updated: add section "Manual Testing Database Reset" to developer manual
Date: Sun, 25 Sep 2022 19:42:36 +0200

This is an automated email from the git hooks/post-receive script.

ttn pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 646f35c  add section "Manual Testing Database Reset" to developer 
manual
646f35c is described below

commit 646f35c6025804d6bd7cd197d9a3899facbdd3c2
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Sun Sep 25 13:41:35 2022 -0400

    add section "Manual Testing Database Reset" to developer manual
---
 taler-developer-manual.rst | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst
index 486db32..09f38b8 100644
--- a/taler-developer-manual.rst
+++ b/taler-developer-manual.rst
@@ -49,6 +49,25 @@ For full ``make check`` support, install these programs:
 The ``make check`` should be able to function without them, but
 their presence permits some tests to run that would otherwise be skipped.
 
+Manual Testing Database Reset
+-----------------------------
+
+Sometimes ``make check`` will fail with some kind of database (SQL)
+error, perhaps with a message like ``OBJECT does not exist`` in the
+``test-suite.log`` file, where ``OBJECT`` is the name of a table or function.
+In that case, it may be necessary to reset the ``talercheck`` database
+with the commands:
+
+.. code-block:: console
+
+   $ dropdb talercheck
+   $ createdb talercheck
+
+This is because, at the moment, there is no support for
+doing these steps automatically in the ``make check`` flow.
+
+(If ``make check`` still fails after the reset, file a bug report as usual.)
+
 Bug Tracking
 ------------
 

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]