List iterator logging problem (html build log)

FinalBuilder Discussion
1

Hi,

I've been testing final builder version 7.0.0.2056 and i seem to have a few problems with list iterators and logging. I use the Export Log action at the end to export the build log and let it email to me using send mail action. But the log is weird when it comes to list iterators, these are the problems i seem to be getting:

1) log shows the action from the list iterator 4 times even though it loops only 3 times

2) List iterator variabele is updated "too late", for the first log entry my list iterator parameter value is empty then it starts the child node (the action it needs to repeat using the iterator) and repeats this for all iterations but in the log it acts like the correct iterator values are logged / displayed after the child node had been exectued like this:

Build Projects in Dproj.txt 14:26:36 14:26:50 00:00:14
Completed
Read Text File "d:\autoBuild\dproj.txt" in variable DprojFileContents 14:26:36 14:26:36 00:00:00
Completed
Building Project 14:26:36 14:26:36 00:00:00
Completed
Building Delphi Win32 "D:\DcProgs\Delphi 2007\DcsTools\Dcsvcl.dpk" 14:26:36 14:26:38 00:00:02
Completed
Building Project "D:\DcProgs\Delphi 2007\DcsTools\Dcsvcl.dpk" 14:26:38 14:26:38 00:00:00
Completed
Building Delphi Win32 "D:\DcProgs\Delphi 2007\Nota\Agenda\DcsPlan\AgLib.dpk" 14:26:38 14:26:39 00:00:00
Completed
Building Project "D:\DcProgs\Delphi 2007\Nota\Agenda\DcsPlan\AgLib.dpk" 14:26:39 14:26:39 00:00:00
Completed
Building Delphi Win32 "D:\DcProgs\Delphi 2007\Nota\Super Medewerker\Smw.dpr" 14:26:39 14:26:50 00:00:10
Completed
Building Project 3 of 3 "D:\DcProgs\Delphi 2007\Nota\Super Medewerker\Smw.dpr" 14:26:50 14:26:50 00:00:00
Completed

That doesn't look right to me.

3) i am not able or don't know how to disable the logging part for the list iterator without also disabling logging for the child actions of the iterator action. When i choose hide from log it hides also the child items

 

I'm perfectly happy if i could just hide it but not for the child nodes if that's not possible how can i get around the problem of the list iterator acting up in the build log and writing one log entry too early and the others too late ?

 

Thanks in advance

 

2
  1. As designed… in order for iterators to know when they are done, they need to execute. The last entry in the log just informs you that it found no more items (bearing in mind the iterator has multiple implementations, not all work on simple string list).

    2) I’m not able to reproduce this here, or perhaps I’m not understanding what the problem is?

    3) Again, as designed, a node in the log needs to be parented, if you hide the parent you hide the child.

3

i have included a sample project illustrating my problem for part 2. But i think i wasn't clear enough the problem probably arrises from using the iterator value (variable) in the description of the iterator action. The 1st time it has no value, when executing the childnode the variable is updated and you can use it when comming back to the iterator node it has the previous value. So it seems it's updated to late although this might be as designed as well. The problem is i don't know how i can make a good log entry (name) for this. Have just iterator and then names of the actions from the childnodes seem a bit weird.

I've included a sample project all files should be placed in c:\temp or you can also edit the paths in the project.

How do you let the iterator appear in a log ? the default value ?