[JENKINS-72577] Revert "Increase MavenTest#sensitiveParameters() timeout to 500s"

[dduportal]

See JENKINS-72577.

Reverts #8840 which was a workaround for slow tests in the ci.jenkins.io's agents infrastructure as described in jenkins-infra/helpdesk#3890.

In the past 4 months, a lot of changes had been applied to the underlying infrastructure such as:

• JDK21 upgrade to 21.0.3+9
• Underlying Linux machines upgraded to powerful ones
• Underlying network fixed
• Agents workload fully migrated to an unified Azure cloud
• etc.

Fixes jenkins-infra/helpdesk#3890

Testing done

I can see that the last "main" branch test (see https://ci.jenkins.io/job/Core/job/jenkins/job/master/6227/testReport/hudson.tasks/MavenTest/) is around ~6s on Linux (on ALL JDKs) and ~13s on Windows (JDK17):

Proposed changelog entries

• Remove test timeout workaround added in Increase MavenTest#sensitiveParameters() timeout to 500s #8840

Proposed upgrade guidelines

N/A

Desired reviewers

@Not-NotMyFault @basil

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[basil]

Many thanks for the performance improvements on the underlying infrastructure that have allowed this temporary workaround to be reverted.

[timja]

Thanks I removed the timeout which was added for the same issue it was just increased once

---

/label ready-for-merge

---

This PR is now ready for merge, after the build has passed, we will merge it if there's no negative feedback.

Thanks!