Update maven-verifier to 2.x #1842
Conversation
laeubi
force-pushed
the
update_verifier
branch
from
f5f7bc2 to
c9abdc1
Compare
Test Results356 files ±0 356 suites ±0 2h 18m 39s ⏱️ - 14m 5s For more details on these failures and errors, see this check. Results for commit bc68ade. ± Comparison against base commit 95199fa. ♻️ This comment has been updated with latest results. |
|
I got the verifier update successful now with only a few exceptions, so if anyone like to help with this it would be welcome, at the moment I have no idea what can cause this maybe something with passing the arguments. |
laeubi
force-pushed
the
update_verifier
branch
3 times, most recently
from
23cadcd to
a808807
Compare
|
@akurtakov maybe something you can help with as well after M1? I got most things fixed now but there are 5 failing test left after the upgrade to Maven Verifier 2.x I just don't understand what might cause this change in behavior .. but probably we just see a bug here that was not discovered previously? The most notable changes for Verifier 2.x is that method names changed and arguments are no longer parsed and passed "as is" but I can't see why it should make a difference here, still a second pair of eyes might reveal something. Next thing is that Verifier 2 executes in the same process by default instead of forking, I have disabled that so we always fork because some test don't work well with it, so it should not be an issue here. |
|
I have the will but no promises :) |
akurtakov
force-pushed
the
update_verifier
branch
from
a808807 to
7e38006
Compare
laeubi
force-pushed
the
update_verifier
branch
from
ec556bc to
78702e6
Compare
laeubi
force-pushed
the
update_verifier
branch
from
78702e6 to
bc68ade
Compare
|
Rebased... |
|
Maybe one should first finish this one as a smaller increment: |
|
@dependabot rebase |
This is not a dependabot PR ;-) I can try to rebase this and resolve conflicts but last time there where still some testfailures du to the upgrade so someone must be look into this if we want to upgrade. |
|
I would probably not find time to look into it as it's just M1 but I'll try to handle some of the deprecations done in this PR separately so it becomes less of a churn. |
No description provided.