Forum member

avishnyakov

27 posts

Posts by avishnyakov

  1. NCrunch Grid Node server pre-configuration

    [quote=Remco;11712][quote=avishnyakov;11711]Looks good. Would the password value remain the same across different VMs? [/quote] Yes, the hash should be the same across environments.[/quote] Works well, thanks! Here is DSC magic for other folks who may be interested. A very minimal config wi…

    22 Jan 2018 02:43 UTC

  2. NCrunch Grid Node server pre-configuration

    Looks good. Would the password value remain the same across different VMs?

    18 Jan 2018 06:33 UTC

  3. NCrunch Grid Node server pre-configuration

    Where does grid node store its configuration and how pre-create it? In our scenarios, we use PowerShell DSC to deploy 8-10 grid nodes. Installation is a no-brainer, changing service to run under particular creds is also okay, but pre-configuring grid node with setting file is a bit of a mystery. …

    17 Jan 2018 07:26 UTC

  4. IDLE Grid Nodes at the end of the tests run

    Thanks Remco, that helps to understand more about distribution. Surely, at the end we really wanna get these test spread across nodes, not stuck on one node with several spare nodes.

    01 Jun 2016 00:39 UTC

  5. IDLE Grid Nodes at the end of the tests run

    >>Normally for NCrunch to place so many tests in one batch, their expected execution time should be very low (i.e. under one second). I see, understand you now. Let me give it a try and play with it. Also, if this is happening for the first run ever, or over the "re-synch/re-run" all the test, h…

    01 Jun 2016 00:31 UTC

  6. IDLE Grid Nodes at the end of the tests run

    No, fixtures are different. There is no setup or anything else, only tests.

    01 Jun 2016 00:19 UTC

  7. IDLE Grid Nodes at the end of the tests run

    I barely see correlation in the exec time. All test have various, random time from several seconds up to several minutes. Running all from the VS 2013.

    31 May 2016 23:43 UTC

  8. IDLE Grid Nodes at the end of the tests run

    >>When you see this happen, is there any pattern as to how the 50-60 tests are split between different tasks in the processing queue? Well, it seems all the outstanding tests are grouped by the last node on which they were executed. We have either failing tests or time-consuming tests which see…

    31 May 2016 23:18 UTC

  9. IDLE Grid Nodes at the end of the tests run

    As tests take different time to be completed, sometimes we have 4 out of 6 grid nodes doing nothing and the 2 nodes finishing off 40-50 scheduled tests. That happens at the very end of the whole test suit run. Say, we run 500 tests on 6 nodes, close to the 50-60 test left we always have 4-5 spare n…

    25 May 2016 11:30 UTC

  10. Inconsistent build across Grid Nodes

    It is not possible even with VS2013 / VS 2015 build tools installed. Gave up, installed VS2013 on every grid node, seems to fix so it works well for the time being. Pity, would say soved.

    25 May 2016 11:22 UTC

  11. Updating Grid Node cleans up custom log-on account on upgrade

    Fair enough, that can (or even should) be moved to PowerShell based installation/configuration. We are looking into DSC resource for NCrunch Grid node, so that the whole process of managing node install, upgrade and config would be much more simpler.

    24 May 2016 10:53 UTC

  12. Updating Grid Node cleans up custom log-on account on upgrade

    We configure Grid Node service to run under a particular account. While updating grid node to the latest MSI, the log on account is set back to "local system account" Would be nice to preserve account on which the grid mod is configured to run.

    24 May 2016 10:10 UTC

  13. Inconsistent build across Grid Nodes

    Thanks Remco, seems to be the case. Used to have only VS2013 + NCrunch and grid, all was fine. Got VS2015 installed, here we go, started having all that fun. The output says only the folllwing: ..\..\..\..\..\Program Files (x86)\MSBuild\12.0\bin\amd64\Microsoft.Common.CurrentVersion.targets…

    23 May 2016 10:13 UTC

  14. Inconsistent build across Grid Nodes

    It seems that with the recent updates NCrunch gives the following message preventing distributed tests execution: >>NCrunch: The build results for this project are not consistent across all computers within the grid. ** LOTS OF DETAILS HERE* It was not like that before, so it is possible to d…

    23 May 2016 08:51 UTC

  15. Extremely slow file transferring on distributing processing

    Thanks! Guess, sorted. Will update with more insights once we have something new. Thanks for the help, again.

    27 Apr 2016 01:07 UTC

  16. Extremely slow file transferring on distributing processing

    No, ~100M on total. All assemblies are about 1-15M, nothing really big. Thanks! I'll give a try with standard ports setting up NCrunch on 80 or something, will see. Again, with mobile connection all went quite alright. Seems to be the first sync only.

    27 Apr 2016 00:34 UTC

  17. Extremely slow file transferring on distributing processing

    Correct, we have some 3rd part assemblies altogether up to ~100M. Next, that seems to be related to local intranet provider and unusual, random port NCrunch uses. Switching to mobile internet helped, lol. Donno, may be zipping stuff in chunks over back to back file upload will do better? Also,…

    27 Apr 2016 00:11 UTC

  18. Extremely slow file transferring on distributing processing

    We constantly have extremely slow filr transferring with the latest NCrunch version while using distributed processing. It takes an hour or so to get several grid node in sync. NCrunch just stuck at some number, like 11 / 957 or 20/957. Does not say anything, constantly looses connection, starts …

    26 Apr 2016 14:40 UTC

  19. Unattended installation for NCrunch GridNodeServer

    [quote=Remco;7481]Not directly, but this should be possible by scripting a manual installation of the grid node service - see [url=http://www.ncrunch.net/documentation/manual-installation-instructions]http://www.ncrunch.net/documentation/manual-installation-instructions[/url]. Installing the MSI …

    25 Apr 2016 18:46 UTC

  20. Distributed processing node list recommended practises

    NCrunch has a fantastic feature called distributed processing. Frankly saying, that's the only reason we use NCrunch right now. We have about 700 regression/integration tests which are run against 3 different environments. NCrunch helps a lot drastically reducing the amount of time to run tests…

    25 Oct 2015 04:56 UTC