Forum Discussion

completeintern's avatar
completeintern
Occasional Contributor
9 years ago

[Distributed Testing] Some files get corrupted during transfer to slave

Hi,

 

We're trying to implement distributed testing on 4 VMs (win 7x32, win8.1x64, win10x86, win10x64) and it's working fine for the most part, although we're running into a serious issue: some files seem to get corrupted while being transfered to slave machines.

 

It seems that if the path becomes long (around 200 characters, but never more than 260) files are turned into folders.

So for instance C:\folder1\...\folder9\file.xml on master will become C:\folder1\...\folder9\file.xml\ on slave. Needless to say, the resulting folder is empty.

 

It may also happen that TestComplete throws this kind of error:

Cannot create file C:\path\somefile.xml
Perhaps the project files are being used by some application (for instance, by TestComplete). Close this application and try again.

This seems to only happen on the Windows 8.1 x64 machine. While checking the host after this error message, the .xml was in fact a folder. That same file was also corrupted on the other hosts, but TC didn't throw that error and tests were able to start normally.

 

Our test process is as follows:

-Look for an available host

-Restore a clean snapshot (so there is not TC/TE instance running, no project files, only the required softwares are installed)

-Transfer the project files

-Run the tests

 

If we try to click on "Copy Project to Slave" from the hosts manager, we get only one folder on the slave host, named 'Ɇ' (which is empty)

 

Version of TC (master): 10.40.2015.7

Version of TE (master/slaves): 10.40.2018.11

 

 

Any help would be greatly appreciated

Thanks

 

5 Replies

    • completeintern's avatar
      completeintern
      Occasional Contributor

      Hi mtsmith,

       

      Thank you but I have already tried to apply the hotfix, but in vain.

       

      I managed to get TestComplete to work by mapping the project source path on Master to a virtual drive so the path beame a lot shorter. (net use M: \\%COMPUTERNAME%\C$\pathtoproject /persistent:yes, I could've used subst but making it permanent is a bit tricky)

      So both manual and automatic project transfer work fine on TC.

       

      However TestExecute is still showing the same issue, the project does not get copied correctly onto slave machines.

       

      Why would TestComplete and TestExecute behave differently?

      • mtsmith's avatar
        mtsmith
        Contributor

        Are TestExecute and TestComplete both using the same login ID?