Getting the mauve source - Cannot connect to host sourceware.org

[llxia]

trafficstars

We have an issue getting the mauve source Cannot connect to host sourceware.org:2401 in systemtest.getDependency. The following PRs cannot be verified at the moment.

https://github.com/adoptium/aqa-systemtest/pull/489 https://github.com/adoptium/aqa-tests/pull/5711 https://github.com/adoptium/STF/pull/140 https://github.com/adoptium/TKG/pull/633

get-source:
     [exec] Could not read password for host: java.io.FileNotFoundException: /home/jenkins/.cvspass (No such file or directory)
     [exec] Cannot connect to host sourceware.org:2401.
     [exec] Result: 1

https://github.com/adoptium/aqa-systemtest/blob/901f940a97d4a21fa740189e03d5518799c60c14/openjdk.test.mauve/build.xml#L380-L390

just for the record, the job was fine on Oct 27, 2024.

[llxia]

Identified git repos for mauve:

• https://github.com/koadman/mauve - https://darlinglab.org/ seems to be a 1 person shop
• https://github.com/ingelabs/mauve - seems to have had a healthy number of diverse contributors back when it was active

[LongyuZhang]

This is our last successful mauve build link, it can be unjar to find the source code. Thanks.

[smlambert]

Last successful at the adoptium server is here: https://ci.adoptium.net/job/systemtest.getDependency/202/

mauve.jar.zip

[llxia]

https://openj9-jenkins.osuosl.org/job/systemtest.getDependency/51/ still failed. I am considering backing the changes and branching out for the January release.

Moving forward, we should compare source code in the jar (https://github.com/adoptium/aqa-tests/issues/5760#issuecomment-2486600539) with identified mauve git repos and build from the update to date material. We might also want to keep a copy ourselves as a backup in case the personal git repo is deleted.

[llxia]

https://github.com/adoptium/aqa-systemtest/pull/493 https://github.com/adoptium/aqa-tests/pull/5773 https://github.com/adoptium/STF/pull/141 https://github.com/adoptium/TKG/pull/639

[sophia-guo]

Is mauve.jar still needed based on https://github.com/adoptium/aqa-systemtest/pull/494 ? Missing mauve.jar still failed the job https://ci.adoptium.net/job/systemtest.getDependency/228/. Could we remove the archive mauve jar for now archiveArtifacts '**/systemtest_prereqs/mauve/mauve.jar' ?

[sophia-guo]

Ignore my comment, I see mauve.jar is still needed.

[sxa]

I hit similar issues when trying to put the "alternate process" for testing Solaris in place. this comment has a list of the targets affected by mauve being unavailable with the error I was receiving which is listed in this comment which I think is consistent with the earlier comments in this issue. I also tripped up on the regular make compile not pulling this down properly which I put in a fix for in the Solaris test script.

[sxa]

We're going to need to pick an option here, bearing in mind this seems to be a product which is no longer actively maintained:

• Continue to pull from one of the repositories where it is still available
• Remove all the tests that require mauve
• Have a mirror of it (I don't normally like things like this, but sine the system tests require it there may be a valid argument for mirroring the mauve source in the systemtest repo)

[llxia]

Just for the record, Exclude mauve Package getModifiers, DecimalFormat suffix/prefix

[smlambert]

https://github.com/adoptium/aqa-tests/issues/3809

[smlambert]

Snapshot from latest code commit on sourceforge: https://sourceforge.net/code-snapshots/svn/m/ma/mauve/code/mauve-code-r4736-mauve-trunk-src.zip

mauve-code-r4736-mauve-trunk-src.zip

TODO: check if it matches the fileset available from the last downloaded mauve.jar file from sourceware.org, if so, revisit "build from src" story. (Noting that this sourceforge is most recently updated by koadman, which was one of the github repos we were looking at https://github.com/koadman/mauve, which I am not sure we built in our previous trial, but has a 2020 release)