question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Only 1 agent running with multiple projects and --process=Multiple

See original GitHub issue

Using a .nunit file to run multiple projects and --process=Multiple will only run one agent process per time while with version 3.6.1 i was able to run one agent per test project.

The command line i’m using is: nunit3-console InsertAnyPathHere\MyNunitProjFile.nunit --x86 --dispose-runners --process=Multiple

My .nunit file is like this:

<NUnitProject>
  <Settings activeconfig="Release" processModel="Multiple" domainUsage="Default" />
  <Config name="Release" runtimeFramework="net-4.0" binpathtype="Manual">
    <assembly path="folder/folder/folder/MyTestDll.dll" />
    <assembly path="folder/folder/folder/MyTestDll1.dll" />
    <assembly path="folder/folder/folder/MyTestDll2.dll" />
    <assembly path="folder/folder/folder/MyTestDll3.dll" />
    <assembly path="folder/folder/folder/MyTestDll4.dll" />
    <assembly path="folder/folder/folder/MyTestDll5.dll" />
    <assembly path="folder/folder/folder/MyTestDll6.dll" />
    <assembly path="folder/folder/folder/MyTestDll7.dll" />
    <assembly path="folder/folder/folder/MyTestDll8.dll" />
  </Config>
</NUnitProject>

I couldnt find any way to run again, as per version 3.6.1, more than one agent per time.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:14 (11 by maintainers)

github_iconTop GitHub Comments

1reaction
rprousecommented, Nov 14, 2021

@CharliePoole proper tests would be better, but you have a lot on your plate trying to get the release out, so I’d suggest being pragmatic and updating the existing tests.

0reactions
CharliePoolecommented, Nov 16, 2021

Ready for review by @nunit/engine-team. Fixed by counting leaf nodes in the tree of packages rather than using subpackages. After expansion, each leaf node is by definition an assembly.

At the same time changed the code so that the processor count could be injected from the tests, rather than relying on Environment.ProcessorCount and added more tests of the LevelOfParallelism property,

Read more comments on GitHub >

github_iconTop Results From Across the Web

Register one runner to multiple projects - GitLab CI/CD
Is there a way to register a runner with multiple projects from the command line? As in, I am running gitlab-runner register ...
Read more >
Self-Hosted agent pool with multiple agents uses only one ...
Both agents have identical configuration and are running. We are using using Private projects and have 5+ parallel jobs (some bought, ...
Read more >
How to manage multiple projects at once
Managing dependencies between projects. Delivery of one project might only be possible after another project, or a part of another project, has been...
Read more >
single gitlab agent for k8s across multiple projects
I have one project for agent config and another for deploying applications. The only thing in the agent project is the config to...
Read more >
Console and Engine Release Notes
382 Only 1 agent running with multiple projects and --process=Multiple; 418 <TestAssembly.dll>.config files not loaded when using an .nunit project file and ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found