BIND 10 trac1790, updated. 143bbda39fee4d4de19d1aa440fe4715f833dbc4 [master] Check for nonexistent db right after BIND starts

[BIND 10 source code commits]

The branch, trac1790 has been updated
       via  143bbda39fee4d4de19d1aa440fe4715f833dbc4 (commit)
       via  e0040ea6dccec67b46bdf4b13d8b8e97aa1e4c2f (commit)
      from  4e20d036b7ed183e51deb160bb4530e6e7d54eb2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 143bbda39fee4d4de19d1aa440fe4715f833dbc4
Author: Mukund Sivaraman <muks at isc.org>
Date:   Tue May 1 06:19:31 2012 +0530

    [master] Check for nonexistent db right after BIND starts

commit e0040ea6dccec67b46bdf4b13d8b8e97aa1e4c2f
Author: Mukund Sivaraman <muks at isc.org>
Date:   Fri Apr 20 16:38:40 2012 +0530

    [1790] Untabify files

-----------------------------------------------------------------------

Summary of changes:
 .../lettuce/configurations/xfrin/inmem_slave.conf  |    2 +-
 tests/lettuce/features/example.feature             |   12 ++++++------
 .../lettuce/features/inmemory_over_sqlite3.feature |    2 +-
 3 files changed, 8 insertions(+), 8 deletions(-)

-----------------------------------------------------------------------
diff --git a/tests/lettuce/configurations/xfrin/inmem_slave.conf b/tests/lettuce/configurations/xfrin/inmem_slave.conf
index 3e4b368..a6d88ee 100644
--- a/tests/lettuce/configurations/xfrin/inmem_slave.conf
+++ b/tests/lettuce/configurations/xfrin/inmem_slave.conf
@@ -11,7 +11,7 @@
         "database_file": "data/inmem-xfrin.sqlite3",
         "datasources": [ {
             "type": "memory",
-	    "class": "IN",
+            "class": "IN",
             "zones": [ {
                 "origin": "example.org",
                 "file": "data/inmem-xfrin.sqlite3",
diff --git a/tests/lettuce/features/example.feature b/tests/lettuce/features/example.feature
index ca5ffbf..e9ef1f3 100644
--- a/tests/lettuce/features/example.feature
+++ b/tests/lettuce/features/example.feature
@@ -5,7 +5,7 @@ Feature: Example feature
     is intentionally uncommented.
     The later scenarios have comments to show what the test steps do and
     support
-    
+
     Scenario: A simple example
         Given I have bind10 running with configuration example.org.config
         And wait for bind10 stderr message BIND10_STARTED_CC
@@ -29,7 +29,7 @@ Feature: Example feature
         # Underwater, we take advantage of our intialization routines so
         # that we are sure this file does not exist, see
         # features/terrain/terrain.py
-        
+
         # Standard check to test (non-)existence of a file
         # This file is actually automatically
         The file data/test_nonexistent_db.sqlite3 should not exist
@@ -43,6 +43,9 @@ Feature: Example feature
         And wait for bind10 stderr message CMDCTL_STARTED
         And wait for bind10 stderr message AUTH_SERVER_STARTED
 
+        # Now we use the first step again to see if the file has been created
+        The file data/test_nonexistent_db.sqlite3 should exist
+
         bind10 module Auth should be running
         And bind10 module Resolver should not be running
         And bind10 module Xfrout should not be running
@@ -56,16 +59,13 @@ Feature: Example feature
         # use in the start step (for bind 10, that is 'I start bind10 with')
         # See scenario 'Multiple instances' for more.
         Then stop process bind10
-        
-        # Now we use the first step again to see if the file has been created
-        The file data/test_nonexistent_db.sqlite3 should exist
 
     Scenario: example.org queries
         # This scenario performs a number of queries and inspects the results
         # Simple queries have already been show, but after we have sent a query,
         # we can also do more extensive checks on the result.
         # See querying.py for more information on these steps.
-        
+
         # note: lettuce can group similar checks by using tables, but we
         # intentionally do not make use of that here
 
diff --git a/tests/lettuce/features/inmemory_over_sqlite3.feature b/tests/lettuce/features/inmemory_over_sqlite3.feature
index c3ad786..adc1315 100644
--- a/tests/lettuce/features/inmemory_over_sqlite3.feature
+++ b/tests/lettuce/features/inmemory_over_sqlite3.feature
@@ -33,7 +33,7 @@ Feature: In-memory zone using SQLite3 backend
         A query for mail.example.org should have rcode NXDOMAIN
         When I send bind10 the command Xfrin retransfer example.org IN 127.0.0.1 47807
         Then wait for new bind10 stderr message XFRIN_TRANSFER_SUCCESS not XFRIN_XFR_PROCESS_FAILURE
-	Then wait for new bind10 stderr message AUTH_LOAD_ZONE
+        Then wait for new bind10 stderr message AUTH_LOAD_ZONE
 
         A query for www.example.org should have rcode NOERROR
         The answer section of the last query response should be