[Boost-commit] svn:boost r79595 - trunk/tools/build/v2/test

Subject: [Boost-commit] svn:boost r79595 - trunk/tools/build/v2/test
From: jurko.gospodnetic_at_[hidden]
Date: 2012-07-19 00:11:51

Author: jurko
Date: 2012-07-19 00:11:50 EDT (Thu, 19 Jul 2012)
New Revision: 79595
URL: http://svn.boost.org/trac/boost/changeset/79595

Log:
Cleaned up Boost Build's internal 'parallel multi-file actions' tests a bit - removed some dead code and updated description comments.
Text files modified: 
   trunk/tools/build/v2/test/core_parallel_multifile_actions_1.py |    14 +++++++++++---                          
   trunk/tools/build/v2/test/core_parallel_multifile_actions_2.py |    13 +++++++------                           
   2 files changed, 18 insertions(+), 9 deletions(-)

Modified: trunk/tools/build/v2/test/core_parallel_multifile_actions_1.py
==============================================================================
--- trunk/tools/build/v2/test/core_parallel_multifile_actions_1.py	(original)
+++ trunk/tools/build/v2/test/core_parallel_multifile_actions_1.py	2012-07-19 00:11:50 EDT (Thu, 19 Jul 2012)
@@ -5,6 +5,16 @@
 # Distributed under the Boost Software License, Version 1.0.
 # (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)
 
+#   Added to guard against a bug causing targets to be used before they
+# themselves have finished building. This used to happen for targets built by a
+# multi-file action that got triggered by another target.
+#
+# Example:
+#   When target A and target B were declared as created by a single action and
+# target A triggered running that action then, while the action was still
+# running, target B was already reporting as being built causing other targets
+# depending on target A to be built prematurely.
+
 import BoostBuild
 
 t = BoostBuild.Tester(pass_toolset=0, pass_d0=False)
@@ -49,13 +59,11 @@
 .use.1 u1.user : g1.generated ;
 .use.2 u2.user : g2.generated ;
 
-NOTFILE root ;
-DEPENDS g1.generated g2.generated : root ;
 DEPENDS all : u1.user u2.user ;
 """)
 
 t.run_build_system(["-ffile.jam", "-j2"], stdout="""\
-...found 6 targets...
+...found 5 targets...
 ...updating 4 targets...
 .gen. g1.generated
 001

Modified: trunk/tools/build/v2/test/core_parallel_multifile_actions_2.py
==============================================================================
--- trunk/tools/build/v2/test/core_parallel_multifile_actions_2.py	(original)
+++ trunk/tools/build/v2/test/core_parallel_multifile_actions_2.py	2012-07-19 00:11:50 EDT (Thu, 19 Jul 2012)
@@ -7,15 +7,16 @@
 
 #   Added to guard against a bug causing targets to be used before they
 # themselves have finished building. This used to happen for targets built by a
-# multi-file action that got triggered by another target, except when the target
-# triggering the action was the first one in the list of targets produced by
-# that action.
+# multi-file action that got triggered by another target, except when the
+# target triggering the action was the first one in the list of targets
+# produced by that action.
 #
 # Example:
 #   When target A and target B were declared as created by a single action with
-# A being the first one listed, and target B triggered running that action then
-# while the action was still running, target A was already reporting as being
-# built causing other targets depending on target A to be built prematurely.
+# A being the first one listed, and target B triggered running that action
+# then, while the action was still running, target A was already reporting as
+# being built causing other targets depending on target A to be built
+# prematurely.
 
 import BoostBuild