Conversation
Bumps [maven-surefire-plugin](https://github.com/apache/maven-surefire) from 2.22.2 to 3.0.0. - [Release notes](https://github.com/apache/maven-surefire/releases) - [Commits](apache/maven-surefire@surefire-2.22.2...surefire-3.0.0) --- updated-dependencies: - dependency-name: org.apache.maven.plugins:maven-surefire-plugin dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Test Results 978 files ±0 978 suites ±0 1h 17m 43s ⏱️ + 2m 20s Results for commit 4981282. ± Comparison against base commit 0ab8cc9. This pull request removes 2 and adds 2 tests. Note that renamed tests count towards both.This pull request removes 2 skipped tests and adds 2 skipped tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
…ven-surefire-plugin-3.0.0
|
This needs to be fixed somehow or then surefire 3.0.0 is somehow broken
|
This is because the test is writing an empty @Artur- Since the test only checks that |
|
Sounds perfectly fine |
|
Slow tests still has issues Sounds a like the failsafe 3.0 issue.. |
|
Thanks. I'll take a look |
|
Ok, so this is a known issue Basically, Using builder.redirectInput(ProcessBuilder.Redirect.PIPE);
builder.redirectError(ProcessBuilder.Redirect.PIPE);BTW, a similar issue with stdio redirection errors was reported previously for Payara and Vaadin 23 with webpack |
|
Oh it was in surefire and not failsafe.. I created that issue |
|
What is the difference between |
|
Just a side note: The test case in https://github.com/vaadin/flow/blob/upgrade-test-runners/flow-server/src/test/java/com/vaadin/flow/server/frontend/TaskRunPnpmInstallTest.java is not marked as |
Right. I was looking at |
|
Kudos, SonarCloud Quality Gate passed!
|
|
So the problem is the opposite |
|
Makes sense. Should we merge this now, as it works? |
|
Yes, I think we can merge this |
|
Maybe the same PRs also fix #16450? |
|
It is probable. Let me try to bump failsafe in the draft PR and let's see what happens |








Bumps maven-surefire-plugin from 2.22.2 to 3.0.0.
Release notes
Sourced from maven-surefire-plugin's releases.
... (truncated)
Commits
41b640b[maven-release-plugin] prepare release surefire-3.0.01b49cdb[SUREFIRE-2156] Refresh download page6669b03[SUREFIRE-2150] Remove duplicate license headersc6ccef3Don't fast break builds on GitHub2709f76[SUREFIRE-2154] Get rid of localRepository from surefire mojo parameter, use ...052ce53[SUREFIRE-2150] upgrade to parent pom 39 (#614)208eae2Sanitize failIfNoSpecifiedTests prefix in failsafeb8246dc[SUREFIRE-2143] Fix reporting of skipped parameterized test11bbdc9[SUREFIRE-2149] Make all ITs run with Maven 3.9.01f0c261remove this file, not sure why this was here...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)