ADDED   docs/manual/bisecting.dot
Index: docs/manual/bisecting.dot
==================================================================
--- /dev/null
+++ docs/manual/bisecting.dot
@@ -0,0 +1,31 @@
+//  Copyright 2021, Matthew Welland.
+// 
+// This file is part of Megatest.
+// 
+//     Megatest is free software: you can redistribute it and/or modify
+//     it under the terms of the GNU General Public License as published by
+//     the Free Software Foundation, either version 3 of the License, or
+//     (at your option) any later version.
+// 
+//     Megatest is distributed in the hope that it will be useful,
+//     but WITHOUT ANY WARRANTY; without even the implied warranty of
+//     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+//     GNU General Public License for more details.
+// 
+//     You should have received a copy of the GNU General Public License
+//     along with Megatest.  If not, see <http://www.gnu.org/licenses/>.
+//
+digraph G {
+    rankdir=LR
+    subgraph cluster_1 {
+        node [style=filled,shape=box];
+
+	B [label="B\nProblem is here"];
+	E [label="E\nProblem manifests here"];
+	A -> B;
+	B -> C;
+	C -> D;
+	D -> E;
+    }
+
+}

ADDED   docs/manual/debugging.txt
Index: docs/manual/debugging.txt
==================================================================
--- /dev/null
+++ docs/manual/debugging.txt
@@ -0,0 +1,75 @@
+//  Copyright 2021, Matthew Welland.
+// 
+// This file is part of Megatest.
+// 
+//     Megatest is free software: you can redistribute it and/or modify
+//     it under the terms of the GNU General Public License as published by
+//     the Free Software Foundation, either version 3 of the License, or
+//     (at your option) any later version.
+// 
+//     Megatest is distributed in the hope that it will be useful,
+//     but WITHOUT ANY WARRANTY; without even the implied warranty of
+//     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+//     GNU General Public License for more details.
+// 
+//     You should have received a copy of the GNU General Public License
+//     along with Megatest.  If not, see <http://www.gnu.org/licenses/>.
+
+Debugging
+---------
+
+A word on Bisecting
+~~~~~~~~~~~~~~~~~~~
+
+Bisecting is a debug strategy intended to speed up finding the root
+cause.
+
+["graphviz", "bisecting.png"]
+----------------------------------------------------------------------
+include::bisecting.dot[]
+----------------------------------------------------------------------
+
+It is common to start debugging where the problem was observed and
+then work back. However by inspecting the output at stage "C" in the
+example above you would potentially save a lot of debug effort.
+
+Examining The Environment
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Test Control Panel - xterm
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+From the dashboard click on a test PASS/FAIL button. This brings up a
+test control panel. Aproximately near the center left of the window
+there is a button "Start Xterm". Push this to get an xterm with the
+full context and environment loaded for that test. You can run scripts
+or ezsteps by copying from the testconfig (hint, load up the
+testconfig in a separate text editor window). This is the easiest
+way to debug your tests.
+
+During Config File Processing
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+It is often helpful to know the content of variables in various
+contexts as Megatest does the actions needed to run your tests. A handy technique is to force the startup of an xterm in the context being examined.
+
+For example, if an item list is not being generated as expected you
+can inject the startup of an xterm as if it were an item:
+
+.Original items table
+-----------------
+[items]
+CELLNAME [system getcellname.sh]
+-----------------
+
+.Items table modified for debug
+-----------------
+[items]
+DEBUG [system xterm]
+CELLNAME [system getcellnames.sh]
+-----------------
+
+When this test is run an xterm will pop up. In that xterm the
+environment is exactly that in which the script "getcellnames.sh"
+would run. You can now debug the script to find out why it isn't
+working as expected.

Index: docs/manual/howto.txt
==================================================================
--- docs/manual/howto.txt
+++ docs/manual/howto.txt
@@ -110,15 +110,15 @@
 # if defined and not "no" flexi-launcher will bypass launcher unless there is no
 # match.
 flexi-launcher yes
 ------------------------
 
-Tricks
-------
+Tricks and Tips
+---------------
 
-This section is a compendium of a various useful tricks for debugging,
-configuring and generally getting the most out of Megatest.
+This section is a collection of a various useful tricks for that
+didn't quite fit elsewhere.
 
 Limiting your running jobs
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The following example will limit a test in the jobgroup "group1" to no more than 10 tests simultaneously.
@@ -136,50 +136,10 @@
 [jobgroups]
 group1 10
 custdes 4
 ---------------
 
-Debugging Tricks
-----------------
-
-Examining The Environment
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Test Control Panel - xterm
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-From the dashboard click on a test PASS/FAIL button. This brings up a test control panel. Aproximately near the center left of the 
-window there is a button "Start Xterm". Push this to get an xterm with the full context and environment loaded for that test. You can run
-scripts or ezsteps by copying from the testconfig (hint, load up the testconfig in a separate gvim or emacs window). This is the easiest way
-to debug your tests.
-
-During Config File Processing
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-It is often helpful to know the content of variables in various
-contexts as Megatest does the actions needed to run your tests. A handy technique is to force the startup of an xterm in the context being examined.
-
-For example, if an item list is not being generated as expected you
-can inject the startup of an xterm as if it were an item:
-
-.Original items table
------------------
-[items]
-CELLNAME [system getcellname.sh]
------------------
-
-.Items table modified for debug
------------------
-[items]
-DEBUG [system xterm]
-CELLNAME [system getcellnames.sh]
------------------
-
-When this test is run an xterm will pop up. In that xterm the
-environment is exactly that in which the script "getcellnames.sh"
-would run. You can now debug the script to find out why it isn't
-working as expected.
 
 Organising Your Tests and Tasks
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 The default location "tests" for storing tests can be extended by

Index: docs/manual/megatest_manual.html
==================================================================
--- docs/manual/megatest_manual.html
+++ docs/manual/megatest_manual.html
@@ -1,10 +1,10 @@
 <!DOCTYPE html>
 <html lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta name="generator" content="AsciiDoc 8.6.7">
+<meta name="generator" content="AsciiDoc 9.0.0rc1">
 <title>The Megatest Users Manual</title>
 <style type="text/css">
 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
 
 /* Default font. */
@@ -84,14 +84,20 @@
   margin-top: 0;
 }
 ul > li     { color: #aaa; }
 ul > li > * { color: black; }
 
-pre {
+.monospaced, code, pre {
+  font-family: "Courier New", Courier, monospace;
+  font-size: inherit;
+  color: navy;
   padding: 0;
   margin: 0;
 }
+pre {
+  white-space: pre-wrap;
+}
 
 #author {
   color: #527bbd;
   font-weight: bold;
   font-size: 1.1em;
@@ -216,11 +222,11 @@
   border-left: 3px solid #dddddd;
   padding-left: 0.5em;
 }
 
 div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
+span.image img { border-style: none; vertical-align: text-bottom; }
 a.image:visited { color: white; }
 
 dl {
   margin-top: 0.8em;
   margin-bottom: 0.8em;
@@ -412,16 +418,10 @@
 /*
  * xhtml11 specific
  *
  * */
 
-tt {
-  font-family: "Courier New", Courier, monospace;
-  font-size: inherit;
-  color: navy;
-}
-
 div.tableblock {
   margin-top: 1.0em;
   margin-bottom: 1.5em;
 }
 div.tableblock > table {
@@ -432,11 +432,11 @@
   color: #527bbd;
 }
 p.table {
   margin-top: 0;
 }
-/* Because the table frame attribute is overriden by CSS in most browsers. */
+/* Because the table frame attribute is overridden by CSS in most browsers. */
 div.tableblock > table[frame="void"] {
   border-style: none;
 }
 div.tableblock > table[frame="hsides"] {
   border-left-style: none;
@@ -451,16 +451,10 @@
 /*
  * html5 specific
  *
  * */
 
-.monospaced {
-  font-family: "Courier New", Courier, monospace;
-  font-size: inherit;
-  color: navy;
-}
-
 table.tableblock {
   margin-top: 1.0em;
   margin-bottom: 1.5em;
 }
 thead, p.tableblock.header {
@@ -536,10 +530,12 @@
 }
 
 @media print {
   body.manpage div#toc { display: none; }
 }
+
+
 @media screen {
   body {
     max-width: 50em; /* approximately 80 characters wide */
     margin-left: 16em;
   }
@@ -808,22 +804,17 @@
 </div>
 </div>
 <div class="sect1">
 <h2 id="_why_megatest">Why Megatest?</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>The Megatest project was started for two reasons, the first was an
-immediate and pressing need for a generalized tool to manage a suite
-of regression tests and the second was the fact that I had written or
-maintained several such tools at different companies over the years. I
-thought a single open source tool, flexible enough to meet the needs
-of any team doing continuous integration and or running a complex
-suite of tests for release qualification would solve some problems for
-me and for others.</p></div>
-<div class="literalblock">
-<div class="content monospaced">
-<pre>-- Matt Welland, original author of the Megatest tool suite.</pre>
-</div></div>
+<div class="paragraph"><p>Megatest was created to provide a generalized tool for managing suites
+of regression tests and to provide a multi-host, distributed
+alternative to "make". The EDA world is littered with proprietory,
+company-specific tools for this purpose and by going open source and
+keeping the tool flexible the hope is that Megatest could be useful to
+any team at any company for continuous integration and almost any
+other general automation tasks.</p></div>
 </div>
 </div>
 <div class="sect1">
 <h2 id="_megatest_design_philosophy">Megatest Design Philosophy</h2>
 <div class="sectionbody">
@@ -959,15 +950,10 @@
 <img src="megatest-system-architecture.png" alt="Static">
 </div>
 </div>
 </div>
 </div>
-</div>
-<div class="sect1">
-<h2 id="_road_map">Road Map</h2>
-<div class="sectionbody">
-</div>
 </div>
 <div class="sect1">
 <h2 id="_todo_road_map">TODO / Road Map</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>Note: This road-map is a wish list and not a formal plan. Items are in
@@ -1941,10 +1927,65 @@
 <div class="paragraph"><p>This test runs a single step called "stepname1" which runs a script
 "stepname.sh". Note that although it is common to put the actions
 needed for a test step into a script it is not necessary.</p></div>
 </div>
 </div>
+</div>
+<div class="sect1">
+<h2 id="_debugging">Debugging</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_a_word_on_bisecting">A word on Bisecting</h3>
+<div class="paragraph"><p>Bisecting is a debug strategy intended to speed up finding the root
+cause.</p></div>
+<div class="imageblock graphviz">
+<div class="content">
+<img src="bisecting.png" alt="bisecting.png">
+</div>
+</div>
+<div class="paragraph"><p>It is common to start debugging where the problem was observed and
+then work back. However by inspecting the output at stage "C" in the
+example above you would potentially save a lot of debug effort.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_examining_the_environment">Examining The Environment</h3>
+<div class="sect3">
+<h4 id="_test_control_panel_xterm">Test Control Panel - xterm</h4>
+<div class="paragraph"><p>From the dashboard click on a test PASS/FAIL button. This brings up a
+test control panel. Aproximately near the center left of the window
+there is a button "Start Xterm". Push this to get an xterm with the
+full context and environment loaded for that test. You can run scripts
+or ezsteps by copying from the testconfig (hint, load up the
+testconfig in a separate text editor window). This is the easiest
+way to debug your tests.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_during_config_file_processing">During Config File Processing</h4>
+<div class="paragraph"><p>It is often helpful to know the content of variables in various
+contexts as Megatest does the actions needed to run your tests. A handy technique is to force the startup of an xterm in the context being examined.</p></div>
+<div class="paragraph"><p>For example, if an item list is not being generated as expected you
+can inject the startup of an xterm as if it were an item:</p></div>
+<div class="listingblock">
+<div class="title">Original items table</div>
+<div class="content monospaced">
+<pre>[items]
+CELLNAME [system getcellname.sh]</pre>
+</div></div>
+<div class="listingblock">
+<div class="title">Items table modified for debug</div>
+<div class="content monospaced">
+<pre>[items]
+DEBUG [system xterm]
+CELLNAME [system getcellnames.sh]</pre>
+</div></div>
+<div class="paragraph"><p>When this test is run an xterm will pop up. In that xterm the
+environment is exactly that in which the script "getcellnames.sh"
+would run. You can now debug the script to find out why it isn&#8217;t
+working as expected.</p></div>
+</div>
+</div>
+</div>
 </div>
 <div class="sect1">
 <h2 id="_how_to_do_things">How To Do Things</h2>
 <div class="sectionbody">
 <div class="sect2">
@@ -2036,14 +2077,14 @@
 </div></div>
 </div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_tricks">Tricks</h2>
+<h2 id="_tricks_and_tips">Tricks and Tips</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>This section is a compendium of a various useful tricks for debugging,
-configuring and generally getting the most out of Megatest.</p></div>
+<div class="paragraph"><p>This section is a collection of a various useful tricks for that
+didn&#8217;t quite fit elsewhere.</p></div>
 <div class="sect2">
 <h3 id="_limiting_your_running_jobs">Limiting your running jobs</h3>
 <div class="paragraph"><p>The following example will limit a test in the jobgroup "group1" to no more than 10 tests simultaneously.</p></div>
 <div class="paragraph"><p>In your testconfig:</p></div>
 <div class="listingblock">
@@ -2056,49 +2097,10 @@
 <div class="content monospaced">
 <pre>[jobgroups]
 group1 10
 custdes 4</pre>
 </div></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_debugging_tricks">Debugging Tricks</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_examining_the_environment">Examining The Environment</h3>
-<div class="sect3">
-<h4 id="_test_control_panel_xterm">Test Control Panel - xterm</h4>
-<div class="paragraph"><p>From the dashboard click on a test PASS/FAIL button. This brings up a test control panel. Aproximately near the center left of the
-window there is a button "Start Xterm". Push this to get an xterm with the full context and environment loaded for that test. You can run
-scripts or ezsteps by copying from the testconfig (hint, load up the testconfig in a separate gvim or emacs window). This is the easiest way
-to debug your tests.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_during_config_file_processing">During Config File Processing</h4>
-<div class="paragraph"><p>It is often helpful to know the content of variables in various
-contexts as Megatest does the actions needed to run your tests. A handy technique is to force the startup of an xterm in the context being examined.</p></div>
-<div class="paragraph"><p>For example, if an item list is not being generated as expected you
-can inject the startup of an xterm as if it were an item:</p></div>
-<div class="listingblock">
-<div class="title">Original items table</div>
-<div class="content monospaced">
-<pre>[items]
-CELLNAME [system getcellname.sh]</pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Items table modified for debug</div>
-<div class="content monospaced">
-<pre>[items]
-DEBUG [system xterm]
-CELLNAME [system getcellnames.sh]</pre>
-</div></div>
-<div class="paragraph"><p>When this test is run an xterm will pop up. In that xterm the
-environment is exactly that in which the script "getcellnames.sh"
-would run. You can now debug the script to find out why it isn&#8217;t
-working as expected.</p></div>
-</div>
 <div class="sect3">
 <h4 id="_organising_your_tests_and_tasks">Organising Your Tests and Tasks</h4>
 <div class="paragraph"><p>The default location "tests" for storing tests can be extended by
 adding to your tests-paths section.</p></div>
 <div class="listingblock">
@@ -2340,11 +2342,11 @@
 <div class="sect2">
 <h3 id="_trim_trailing_spaces">Trim trailing spaces</h3>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="/nfs/pdx/disks/ice.disk.002/icfadm/pkgs/asciidoc/8.6.7/images/icons/note.png" alt="Note">
+<img src="/usr/images/icons/note.png" alt="Note">
 </td>
 <td class="content">As of Megatest version v1.6548 trim-trailing-spaces defaults to yes.</td>
 </tr></table>
 </div>
 <div class="listingblock">
@@ -2657,11 +2659,11 @@
 waiton test1 test2</pre>
 </div></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="/nfs/pdx/disks/ice.disk.002/icfadm/pkgs/asciidoc/8.6.7/images/icons/note.png" alt="Note">
+<img src="/usr/images/icons/note.png" alt="Note">
 </td>
 <td class="content">Dynamic waiton lists must be capable of being calculated at the
 beginning of a run. This is because Megatest walks the tree of waitons
 to create the list of tests to execute.</td>
 </tr></table>
@@ -3016,11 +3018,11 @@
 <div class="paragraph"><p>Ezsteps is the recommended way to implement tests and automation in
 Megatest.</p></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="/nfs/pdx/disks/ice.disk.002/icfadm/pkgs/asciidoc/8.6.7/images/icons/note.png" alt="Note">
+<img src="/usr/images/icons/note.png" alt="Note">
 </td>
 <td class="content">Each ezstep must be a single line. Use the [scripts] mechanism
 to create multiline scripts (see example below).</td>
 </tr></table>
 </div>
@@ -3041,11 +3043,11 @@
 step to step. Use this to source script files that modify the
 envionment where the modifications are needed in subsequent steps.</p></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="/nfs/pdx/disks/ice.disk.002/icfadm/pkgs/asciidoc/8.6.7/images/icons/note.png" alt="Note">
+<img src="/usr/images/icons/note.png" alt="Note">
 </td>
 <td class="content">aliases and variables with strange whitespace or characters will
 not propagate correctly. Put in a ticket on the
 <a href="http://www.kiatoa.com/fossils/megatest">http://www.kiatoa.com/fossils/megatest</a> site if you need support for a
 specific strange character combination.</td>
@@ -3229,11 +3231,11 @@
 COMPLETED/ xterm -e bash -s --</pre>
 </div></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="/nfs/pdx/disks/ice.disk.002/icfadm/pkgs/asciidoc/8.6.7/images/icons/note.png" alt="Note">
+<img src="/usr/images/icons/note.png" alt="Note">
 </td>
 <td class="content">There is a trailing space after the double-dash</td>
 </tr></table>
 </div>
 <div class="paragraph"><p>There are a number of environment variables available to the trigger script
@@ -3566,10 +3568,11 @@
 </div>
 <div id="footnotes"><hr></div>
 <div id="footer">
 <div id="footer-text">
 Version 1.5<br>
-Last updated 2020-10-13 21:24:33 PDT
+Last updated
+ 2021-08-30 08:37:04 MST
 </div>
 </div>
 </body>
 </html>

Index: docs/manual/megatest_manual.txt
==================================================================
--- docs/manual/megatest_manual.txt
+++ docs/manual/megatest_manual.txt
@@ -33,20 +33,17 @@
 ----------------------------
 
 Why Megatest?
 -------------
 
-The Megatest project was started for two reasons, the first was an
-immediate and pressing need for a generalized tool to manage a suite
-of regression tests and the second was the fact that I had written or
-maintained several such tools at different companies over the years. I
-thought a single open source tool, flexible enough to meet the needs
-of any team doing continuous integration and or running a complex
-suite of tests for release qualification would solve some problems for
-me and for others.
-
- -- Matt Welland, original author of the Megatest tool suite.
+Megatest was created to provide a generalized tool for managing suites
+of regression tests and to provide a multi-host, distributed
+alternative to "make". The EDA world is littered with proprietory,
+company-specific tools for this purpose and by going open source and
+keeping the tool flexible the hope is that Megatest could be useful to
+any team at any company for continuous integration and almost any
+other general automation tasks.
 
 Megatest Design Philosophy
 --------------------------
 
 Megatest is a distributed system intended to provide the minimum needed
@@ -98,24 +95,26 @@
 which can launch jobs on local and remote Linux hosts. Currently
 megatest uses the network filesystem to call home to your master
 sqlite3 database. Megatest has been used with the Intel Netbatch and
 lsf (also known as openlava) batch systems and it should be
 straightforward to use it with other similar systems.
+
+// :leveloffset: 0
 
 include::overview.txt[]
 
 include::plan.txt[]
-
+ 
 include::installation.txt[]
 
 include::getting_started.txt[]
 
 include::study_plan.txt[]
 
-// :leveloffset: 0
-
 include::writing_tests.txt[]
+
+include::debugging.txt[]
 
 include::howto.txt[]
 
 include::reference.txt[]
 

Index: docs/manual/plan.txt
==================================================================
--- docs/manual/plan.txt
+++ docs/manual/plan.txt
@@ -1,8 +1,5 @@
-Road Map
---------
-
 // This file is part of Megatest.
 // 
 //     Megatest is free software: you can redistribute it and/or modify
 //     it under the terms of the GNU General Public License as published by
 //     the Free Software Foundation, either version 3 of the License, or

Index: docs/manual/server.png
==================================================================
--- docs/manual/server.png
+++ docs/manual/server.png
cannot compute difference between binary files

Index: http-transport.scm
==================================================================
--- http-transport.scm
+++ http-transport.scm
@@ -40,11 +40,11 @@
 
 (include "common_records.scm")
 (include "db_records.scm")
 (include "js-path.scm")
 
-(require-library stml)
+(use stml2)
 (define (http-transport:make-server-url hostport)
   (if (not hostport)
       #f
       (conc "http://" (car hostport) ":" (cadr hostport))))
 

Index: mtut.scm
==================================================================
--- mtut.scm
+++ mtut.scm
@@ -35,11 +35,11 @@
 
 (use ducttape-lib)
 
 (include "megatest-fossil-hash.scm")
 
-(require-library stml)
+(use stml2)
 
 ;; stuff for the mapper and checker functions
 ;;
 (define *target-mappers*  (make-hash-table)) 
 (define *runname-mappers* (make-hash-table)) 

Index: tests.scm
==================================================================
--- tests.scm
+++ tests.scm
@@ -34,11 +34,11 @@
 (declare (uses server))
 ;;(declare (uses stml2))
 
 (use sqlite3 srfi-1 posix regex regex-case srfi-69 dot-locking tcp directory-utils)
 (import (prefix sqlite3 sqlite3:))
-(require-library stml)
+(use stml2)
 
 (include "common_records.scm")
 (include "key_records.scm")
 (include "db_records.scm")
 (include "run_records.scm")