Fix PathRemoverTest timeout in RISC-V devices.

[qyl27]

I am working in Arch Linux RISC-V port.
RISC-V devices have extremely low performance, 10 seconds timeout in PathRemoverTest is too short to pass in these devices.
After my test, changing it to 30 seconds can pass tests.
That is a minor change, so I haven't created an issue in Jira.

Testing done

It simply increases the timeout and is tested in our compile machines.

Proposed changelog entries

• Increase timeout in PathRemoverTest for RISC-V devices.

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

Sorry, I don't know which team should be mentioned.

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).

[welcome]

Yay, your first pull request towards Jenkins core was created successfully! Thank you so much!

A contributor will provide feedback soon. Meanwhile, you can join the chats and community forums to connect with other Jenkins users, developers, and maintainers.

[daniel-beck]

RISC-V devices have extremely low performance, 10 seconds timeout in PathRemoverTest is too short to pass in these devices.
After my test, changing it to 30 seconds can pass tests.

Could you confirm that all other tests pass, including those in test/? I would expect running the Jenkins tests on a low power device being at least impractically slow.

[qyl27]

RISC-V devices have extremely low performance, 10 seconds timeout in PathRemoverTest is too short to pass in these devices.
After my test, changing it to 30 seconds can pass tests.

Could you confirm that all other tests pass, including those in test/? I would expect running the Jenkins tests on a low power device being at least impractically slow.

Yes, It has passed all tests after my patch in HiFive Unmatched.

[timja]

Seems fine

[welcome]

Congratulations on getting your very first Jenkins core pull request merged 🎉🥳

This is a fantastic achievement, and we're thrilled to have you as part of our community! Thank you for your valuable input, and we look forward to seeing more of your contributions in the future!

We would like to invite you to join the community chats and forums to meet other Jenkins contributors 😊
Don't forget to check out the participation page to learn more about how to contribute to Jenkins.