You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are experiencing inconsistent test case execution times while using GitHub Actions runners with different Ubuntu images. Below are the details:
#11934
Application: Java-based.
Build Tool: Maven.
Testing: Test cases run before deployment to ensure stability.
Deployment: Application is deployed using GitHub Actions.
Error Observed:
"The job running on runner GitHub Actions 42 has exceeded the maximum execution time of 15 minutes."
Timeline:
- Initial State:
Runner Image: ubuntu-22.04 (version 20240714.1.0).
Test cases completed in 9 minutes.
- Issue Observed:
Runner Image updated to ubuntu-22.04 (version 20240721.1.0).
Test case execution time increased to 15+ minutes, causing pipeline failures.
- Temporary Fix:
Added alphabetical to pom.xml, which resolved the issue, reducing the time back to < 15 minutes. However, the root cause remains unknown.
- Subsequent Runner Update:
Runner Image: ubuntu-22.04 (version 20241112.1.0).
Removed alphabetical as tests again started completing in 9 minutes.
- Current Issue:
Migrated to ubuntu-24.04 (version 20241201.1.0).
Test case execution time increased again to 15+ minutes, causing failures.
- Test Configuration:
alphabetical
classes
2
0
false
Adding alphabetical temporarily resolved the issue but its actual impact is unclear.
- Observations:
The issue correlates with changes in GitHub runner image versions.
Execution time changes drastically depending on the runner version.
- Questions:
Why does adding alphabetical reduce execution time?
What changes in the runner images are potentially affecting Maven's performance?
Why does the execution time vary significantly with different runner versions?
Test case should be run without this configuration.
alphabetical
Actual behavior
we are continuing to observe variance in behavior when executing workflows on GitHub-hosted runners. Specifically, the test case execution time fluctuates based on the runner image version in use.
Repro steps
Steps to Reproduce:
Run the test cases using the ubuntu-22.04 runner (version 20240714.1.0) and observe 9 minutes execution time.
Run the same test cases using the ubuntu-22.04 runner (version 20240721.1.0) and observe 15+ minutes execution time.
Add alphabetical to the pom.xml and rerun with version 20240721.1.0, and observe the reduced execution time.
Remove alphabetical and test with ubuntu-24.04 (version 20241201.1.0) to observe the issue reoccurring.
The text was updated successfully, but these errors were encountered:
Hi @dhananjay-quivo - In meantime, could you please provide your build and repro links so that we can debug more into this.
Also, we request you to update your sync process and try with latest Ubuntu 22.04 image version 20250323.1.0. And let us know if you encounter any further issues. Thanks!
Description
Pipeline Overview:
Application: Java-based.
Build Tool: Maven.
Testing: Test cases run before deployment to ensure stability.
Deployment: Application is deployed using GitHub Actions.
Error Observed:
"The job running on runner GitHub Actions 42 has exceeded the maximum execution time of 15 minutes."
Timeline:
- Initial State:
Runner Image: ubuntu-22.04 (version 20240714.1.0).
Test cases completed in 9 minutes.
- Issue Observed:
Runner Image updated to ubuntu-22.04 (version 20240721.1.0).
Test case execution time increased to 15+ minutes, causing pipeline failures.
- Temporary Fix:
Added alphabetical to pom.xml, which resolved the issue, reducing the time back to < 15 minutes. However, the root cause remains unknown.
- Subsequent Runner Update:
Runner Image: ubuntu-22.04 (version 20241112.1.0).
Removed alphabetical as tests again started completing in 9 minutes.
- Current Issue:
Migrated to ubuntu-24.04 (version 20241201.1.0).
Test case execution time increased again to 15+ minutes, causing failures.
- Test Configuration:
alphabetical classes 2 0 false Adding alphabetical temporarily resolved the issue but its actual impact is unclear.- Observations:
The issue correlates with changes in GitHub runner image versions.
Execution time changes drastically depending on the runner version.
- Questions:
Why does adding alphabetical reduce execution time?
What changes in the runner images are potentially affecting Maven's performance?
Why does the execution time vary significantly with different runner versions?
Platforms affected
Runner images affected
Image version and build link
ubuntu-22.04 (version 20240721.1.0).
ubuntu-24.04 version.
Is it regression?
No
Expected behavior
Test case should be run without this configuration.
alphabetical
Actual behavior
we are continuing to observe variance in behavior when executing workflows on GitHub-hosted runners. Specifically, the test case execution time fluctuates based on the runner image version in use.
Repro steps
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: