Action for running tests in parallel#7979
Conversation
extide/gradle/src/org/netbeans/modules/gradle/ActionProviderImpl.java
Outdated
Show resolved
Hide resolved
ide/extexecution.base/src/org/netbeans/api/extexecution/base/ExplicitProcessParameters.java
Outdated
Show resolved
Hide resolved
...a.lsp.server/src/org/netbeans/modules/java/lsp/server/debugging/launch/NbLaunchDelegate.java
Outdated
Show resolved
Hide resolved
java/gradle.test/src/org/netbeans/modules/gradle/test/GradleTestProgressListener.java
Show resolved
Hide resolved
java/gradle.test/src/org/netbeans/modules/gradle/test/GradleTestProgressListener.java
Show resolved
Hide resolved
java/maven/src/org/netbeans/modules/maven/execute/AbstractOutputHandler.java
Show resolved
Hide resolved
java/maven/src/org/netbeans/modules/maven/execute/MavenCommandLineExecutor.java
Outdated
Show resolved
Hide resolved
java/maven/src/org/netbeans/modules/maven/execute/MavenCommandLineOptions.java
Outdated
Show resolved
Hide resolved
java/maven/src/org/netbeans/modules/maven/execute/cmd/ExecMojo.java
Outdated
Show resolved
Hide resolved
java/maven/src/org/netbeans/modules/maven/execute/model/NetbeansActionMapping.java
Show resolved
Hide resolved
ide/projectapi/src/org/netbeans/spi/project/ContainedProjectFilter.java
Outdated
Show resolved
Hide resolved
java/gradle.test/src/org/netbeans/modules/gradle/test/GradleTestProgressListener.java
Outdated
Show resolved
Hide resolved
java/java.lsp.server/src/org/netbeans/modules/java/lsp/server/progress/TestProgressHandler.java
Outdated
Show resolved
Hide resolved
java/maven/src/org/netbeans/modules/maven/execute/MavenCommandLineExecutor.java
Outdated
Show resolved
Hide resolved
java/java.lsp.server/src/org/netbeans/modules/java/lsp/server/progress/ModuleInfo.java
Outdated
Show resolved
Hide resolved
java/java.lsp.server/src/org/netbeans/modules/java/lsp/server/progress/TestProgressHandler.java
Outdated
Show resolved
Hide resolved
.../java.lsp.server/src/org/netbeans/modules/java/lsp/server/protocol/WorkspaceServiceImpl.java
Outdated
Show resolved
Hide resolved
| "javadoc", //NOI18N | ||
| COMMAND_TEST, | ||
| COMMAND_TEST_SINGLE, | ||
| COMMAND_TEST_PARALLEL, |
There was a problem hiding this comment.
bump dependency version on project.api
d717d00 to
a8c4d23
Compare
c3ae922 to
54b4326
Compare
|
@neilcsmith-net please advise how to fix build failure https://github.com/apache/netbeans/actions/runs/12162766052/job/33936238338?pr=7979 related to signature check. There's a (formally) incompatible change on friend-only API. |
mbien
left a comment
There was a problem hiding this comment.
was this tested with mvnd? mvnd builds multithreaded by default, mvn builds singlethreaded by default (without extra flags).
java/maven.junit/src/org/netbeans/modules/maven/junit/JUnitOutputListenerProvider.java
Outdated
Show resolved
Hide resolved
|
@sdedic sorry, I'd missed that the addition was incompatible. Am not involved with releases at the moment, and only commented after a glance at this to try and save @ebarboni some headaches post NB24. If this has to go in as is, then either wait for the API sigs to merge in a week or so and rebase, manually patch the 3 required lines into the sig file (which should pass then?), or merge and be prepared to help Eric with the API signature integration post release. OTOH, either the test is relevant or not? Add the methods as default on the interface, as you did in the last change to that file to not require changes to pass tests? Or lets just stop having sigtests for friend APIs as they're irrelevant - the build will pick up internal breakage, and we don't support external usage. Our process for handling sig tests for releases could do with a review anyway. I have some ideas how to improve that, but we have the one we have for now. |
|
@mbien I tried with |
cb073da to
dfa178e
Compare
|
@ebarboni When can we expect sigs to be generated for the release, since this PR should (probably) introduce changes to .sig? |
|
@petrovic-d follow #8034 |
|
sig pr merged |
55cabe8 to
5d62a2f
Compare
java/java.lsp.server/src/org/netbeans/modules/java/lsp/server/progress/TestProgressHandler.java
Outdated
Show resolved
Hide resolved
java/maven/src/org/netbeans/modules/maven/api/execute/RunConfig.java
Outdated
Show resolved
Hide resolved
|
|
||
| static ContainedProjectFilter getProjectFilter(Project prj, Map<String, Object> launchArguments) { | ||
| List<String> projectsArg = argsToStringList(launchArguments.get("projects")); | ||
| List<Project> projects = ProjectUtils.getContainedProjects(prj, false).stream() |
There was a problem hiding this comment.
Note: this does not allow to specify projects nested more levels in the project's hierarchy. Not a bug, and can be enhanced later in a compatible way.
.../java.lsp.server/src/org/netbeans/modules/java/lsp/server/protocol/WorkspaceServiceImpl.java
Show resolved
Hide resolved
| * | ||
| * @since 1.99 | ||
| */ | ||
| public final class NestedClass { |
There was a problem hiding this comment.
Not really a request to change anything, just an observation: this whole angle around NestedClass seems mostly orthogonal to the run tests in parallel feature, and could probably have been a separate PR.
8143039 to
40bae1a
Compare
|
@petrovic-d assuming rebase & squash |
|
Hi, any chance of reusing these changes to also support what #3995 was intended to do? |
@matyasberry Hi, this PR should also add support for nested classes -> see this |
New action for running tests in parallel. It can be invoked via command:
nbls.run.test.parallelCommand support specifying modules for which tests will be ran in parallel. It's up to client to pass the module list, so by default it will run without passed modules.
To test it with module list, it needs to be modified like this:
in
java/java.lsp.server/vscode/src/extension.tsfilemodify line
835to:testAdapter?.run(new vscode.TestRunRequest(), new vscode.CancellationTokenSource().token, true, ["module1", "module2"]);