This is the same previously report Junit Report publishing bug that was first reported in the user forum. This is NOT the same as the bug most recently fixed which caused "WARN - No report generators defined" to show up in the log. This is the original bug where everything seemed to work except on the publishing part, it couldn't find any junit xml files to publish causing, "WARN - There is no input file need publish for 'JUnit Report', [Dir: /d01/QuickBuild/workspace/root/lgcbuilds/DSInfrastructure/dsinfra_native/DS_5000_4_0_0, Pattern: dsinfra-native/build/tests/linux64/xml/*.xml]" to show up in the log.

If you remember, this happens when I try to be very advanced in my node management and have the controller of the entire build (the node that runs the master step) also be used as one of my platform child nodes. This is all described in my original user forum post. So if I send out unit tests to be run on 5 platforms where the master node is used as one of those platforms, this bug occurs some of the time. It is not 100% reproducible. It seems to be some sort of timing issue or workspace lock issue or something. I have 5 parallel steps all executing unit tests on 5 different platform nodes such that one of those platform nodes is the master node. Therefore, if they all finish at the same time causing all to send their output files back to the master node, one of those nodes is sending output files to itself while the other 4 actually have to send the files. Maybe the bug is caused when a different node is sending output files back at the same time the master node is sending files back to itself?

I have checked the logs and I can see NO error during the sending output files step. I do see that the master node sending files to itself is very quick since it shouldn't have to do anything. I do see that the different nodes sending files to the master node takes a few seconds.

My workaround was to NOT reuse the master node as a platform unit test node, but that causes 1 extra node to be used unnecessarily. I was hoping that you fixing the "WARN - No report generators defined" would have fixed this problem too, but apparently not. I really could use a fix for this as it is now in my way from doing other things.

By the way, this was tested against 2.0B9, not 2.0.0.