Forum member

applieddev

19 posts

Posts by applieddev

  1. TeamCity Timeline incorrectly sized for the window

    michaelroes, I have just submitted the Timeline.html via the contact form was there anything else you needed?

    18 Nov 2021 11:55 UTC

  2. TeamCity Timeline incorrectly sized for the window

    Thanks Remco, I look forward any updates you can make

    12 Nov 2021 09:17 UTC

  3. TeamCity Timeline incorrectly sized for the window

    Here's an example of it wrapping columns unnecessarily this is due to width=711px; forced as an inline style on div#container adding min-width=100%; rectifies the issue without any JS changes. it would also be great to reduce the column padding-left from 18px down to 4px, so we can allow for mo…

    09 Nov 2021 10:13 UTC

  4. TeamCity Timeline incorrectly sized for the window

    the NCrunch Timeline is rendering with the wrong width applied to [quote]<div id="container" style="width: 711px;">[/quote] this is causing several node test timelines to wrap beyond the timetrack everytime we investigate we need to override the width style on #container also, we would like to …

    08 Nov 2021 17:30 UTC

  5. Re-run specific tests

    thanks for the explanation Remco we use FullNameMatchesRegex with spaces and that works i've updated our regex match to include the fixture name and that works better [quote](FullNameMatchesRegex '\.ImportFixture\.Import Test$')[/quote] also, extending on samholder's solution, to reduce the …

    19 Oct 2021 09:02 UTC

  6. Re-run specific tests

    we came across the issue of partial regex matches using [b]FullNameMatchesRegex [/b] example test names: [list][*]Import Test [*]Import Test to backup [*]AutoImport Test[/list] [quote](FullNameMatchesRegex 'Import Test')[/quote] then it will run all 3 example tests (as they all match that p…

    18 Oct 2021 10:49 UTC

  7. TeamCity build waits for unneeded NCrunch node build

    Remco, on closer investigation of one of the pairs of test runs, the time for Grid Node Synchronisation does overlap with the other test run busy running a test Normally that shows up in the light grey as "Other Task For: [IP ADDRESS]"

    13 Oct 2021 16:30 UTC

  8. TeamCity build waits for unneeded NCrunch node build

    Remco, from our initial testing of the new version of NCrunch, we havent see the same issue exactly However, we are now seeing Grid Node Synchronisation taking extremely long Taking 8-14 minutes longer than usual Normally it takes around 10-30 seconds It doesnt happen every time, maybe 50% …

    13 Oct 2021 15:51 UTC

  9. TeamCity build waits for unneeded NCrunch node build

    thanks Remco I am coordinating with our Ops team to get this tested on a few of our NCrunch node instances I will let you know how the testing goes

    07 Oct 2021 13:59 UTC

  10. TeamCity build waits for unneeded NCrunch node build

    Thanks Remco! I look forward to any options you can suggest

    07 Oct 2021 08:11 UTC

  11. TeamCity build waits for unneeded NCrunch node build

    We are sharing NCrunch nodes between multiple TeamCity test run builds NCrunch is holding up the TeamCity test run waiting on a node that is not running a test. That node is waiting to build the solution but is busy with another test from a separate TeamCity test run build. How can we tell the …

    06 Oct 2021 09:11 UTC

  12. Test run stops midway with "No data received... Forcing disconnection"

    we finally managed to get the issue again Test results: Tests passed: 0, ignored: 30; where the 30 "ignored" were requested, but failed to run due to "No data received from MACHINENAME within connection timeout period. Forcing disconnection." is that expected outcome? I guess we would need…

    16 Oct 2020 14:55 UTC

  13. Test run stops midway with "No data received... Forcing disconnection"

    thanks Remco, our network engineers assure me that there is no network issues i have removed "/TeamCityDisableTestNotRunFailureReporting" and added "/IgnoredFilteredTestsInRunFailureReporting" just need to wait for the issue to resurface to see we have found that after restarting NCrunch ser…

    15 Oct 2020 10:02 UTC

  14. Test run stops midway with "No data received... Forcing disconnection"

    We are seeing some test builds stop abruptly on TeamCity with "No data received from MACHINENAME within connection timeout period. Forcing disconnection." We queued 29 tests for parallel execution on 1 NCrunch server node "Queuing 29 tests for passive execution" Several tests run (passes) the…

    14 Oct 2020 08:34 UTC

  15. Is there a way to stagger the starting of parallel executed tests?

    We have 80+ tests that get run in parallel. the setup of each test does several service/db calls, which when all run around the same time can overload our test system and cause timeouts. if we could stagger the start of each test by a few seconds, that would relieve the load on our test system and…

    06 May 2020 11:18 UTC

  16. Parallel execution not spreading tests across available processes

    thanks Remco, their execution times are quite consistent and its not always the same tests that get bundled together all the other tests are also Selenium, so they all have the same dependencies, but just a few get bundled together. can i see Expected/Actual Processing Time on NCrunch nodes r…

    15 Apr 2020 09:26 UTC

  17. Parallel execution not spreading tests across available processes

    We're getting an issue with our SpecFlow 3.1 tests running in parallel across multiple NCrunch nodes with many threads available the execution is held up by 1 or 2 processes that run multiple tests, from multiple features / folders, with different tags this increasing our test time from 20 mins …

    14 Apr 2020 15:07 UTC

  18. NCrunch reports tests as failing even though all tests pass, and no indication why.

    I have run feature tests in NCrunch VS Client several times and have not been able to reproduce this issue

    20 Mar 2020 14:40 UTC

  19. NCrunch reports tests as failing even though all tests pass, and no indication why.

    Hi, i work with samholder. I've run the same SpecFlow tests via TeamCity on the same NCrunch server node the first test run has all tests pass and all features pass the second test run has all tests pass and 1 feature fail [list=1] [*]Tests passed: 12, ignored: 261 [*]Tests passed: 12, ignor…

    19 Mar 2020 14:37 UTC