[Scons-users] blocking execution until compilation is done

[edA-qa mort-ora-y]

On 08/10/12 20:55, William Deegan wrote:

>> I'm trying to create a fence which basically says all my build actions

>> have to occur prior to all my check actions. But there is no dependency

>> between all the check and build actions.

> Why is this important? (that all build items finish before any test items are run?)


I have two reasons for this. Firstly is because the test consumes
resources and thus slows down the build process, and the build process
can interfere with the test. This happens when a test uses multiple
threads and I am using many concurrent build jobs. Scons can't
understand that the test requires many processors at once and thus
allocates it only a single slot.

Secondly, because the test output is then interspersed with the build
output. If everything goes fine this isn't a real problem, but when
errors occur this becomes an issue. In my current case the test produces
a lot of output (listing passed cases) and at the same time the
compilation of some other program fails. I can't clearly see the failed
output. If I rerun the same scons command that same output occurs though
since the test will be run again and the compilation will also happen.

Again, my issue is perhaps not vital to a final build of a product. It
is mainly an issue during iterative development on individual modules.
Having a clean separation of building and testing, in a single
command-line,  for one or more targets, provides significant advantage
to the development process.


-- 
edA-qa mort-ora-y
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Sign: Please digitally sign your emails.
Encrypt: I'm also happy to receive encrypted mail.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
Url : <http://four.pairlist.net/pipermail/scons-users/attachments/20121008/cfc0d26b/attachment.pgp>