-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add sample integ tests for latest systemd unit file #17410
Add sample integ tests for latest systemd unit file #17410
Conversation
@peterzhuamazon Here are the sample tests to verify the behavior |
❌ Gradle check result for beaa600: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
@RajatGupta02 I am not sure how exactly this test is supposed to be running, should we run it in Docker with RPM distribution installed? Thank you. |
It will be onboard to opensearch-build repo and run within the framework there. |
Hi @RajatGupta02 @kumargu I made a change to this PR, specially adding I also have changes to build repo which we can build the new deb/rpm with service file and env file from your previous PR (#17107): There might be some changes required for this line, as our docker container is assuming to have 4 CPUs, I wonder if you can use workers by default to avoid overflowing the system.
cc: @getsaurabh02 The result log:
|
Signed-off-by: Rajat Gupta <[email protected]>
❌ Gradle check result for e0e7c61: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Rajat Gupta <[email protected]>
❌ Gradle check result for c1f2677: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Rajat Gupta <[email protected]>
❌ Gradle check result for ccc1b7b: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Seems passing:
|
Signed-off-by: Rajat Gupta <[email protected]>
Signed-off-by: Rajat Gupta <[email protected]>
❌ Gradle check result for 1ff7d59: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 1ff7d59: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Some unrelated tests are failing. Can we re-run this? |
❌ Gradle check result for 1ff7d59: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 1ff7d59: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 1ff7d59: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 1ff7d59: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
@reta The tests pass locally, and gradle testing convention precommit checks pass now, also I do not see any test failures with Gradle Check (Jenkins) workflow so I think we can merge this? |
❌ Gradle check result for 1ff7d59: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
I don't see any test failures here: https://build.ci.opensearch.org/job/gradle-check/54199/testReport/
|
c66fb4a
to
1ff7d59
Compare
Signed-off-by: Rajat Gupta <[email protected]>
Also passes:
|
❌ Gradle check result for d3b1c0a: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
console log:
Not related to our change this time! |
❕ Gradle check result for d3b1c0a: UNSTABLE Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
Description
Added few integ tests for the latest systemd unit file that has to be shipped from version 3.0 onwards.
Supporting References
Related PR: #17107
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.