Temporarily disable long running tests #2431
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request does not have a backport label. Could you fix it @romulets? 🙏
|
romulets
force-pushed
the
temp-disable-pull-request-tests
branch
from
3595354
to
e461be4
Compare
📊 Allure Report - 💚 No failures were reported.
|
romulets
force-pushed
the
temp-disable-pull-request-tests
branch
from
e461be4
to
423feb3
Compare
gurevichdmitry
approved these changes
Aug 14, 2024
Before this change all the PRs were executing these long running jobs, on avg ~15min each run. But the branch with the changes was not the one being tested, rather just main, therefore wasting time and resource. With the ticket elastic/security-team#9129 we will solve this issue. But in the meanwhile, we are disabling these jobs.
romulets
force-pushed
the
temp-disable-pull-request-tests
branch
from
423feb3
to
b8debaa
Compare
mergify bot
pushed a commit
that referenced
this pull request
Oct 17, 2024
Before this change all the PRs were executing these long running jobs, on avg ~15min each run. But the branch with the changes was not the one being tested, rather just main, therefore wasting time and resource. With the ticket https://github.com/elastic/security-team/issues/9129 we will solve this issue. But in the meanwhile, we are disabling these jobs. (cherry picked from commit 48283b6) # Conflicts: # .github/workflows/ci.yml
mergify bot
pushed a commit
that referenced
this pull request
Oct 17, 2024
Before this change all the PRs were executing these long running jobs, on avg ~15min each run. But the branch with the changes was not the one being tested, rather just main, therefore wasting time and resource. With the ticket https://github.com/elastic/security-team/issues/9129 we will solve this issue. But in the meanwhile, we are disabling these jobs. (cherry picked from commit 48283b6) # Conflicts: # .github/workflows/ci.yml
mergify bot
pushed a commit
that referenced
this pull request
Oct 17, 2024
Before this change all the PRs were executing these long running jobs, on avg ~15min each run. But the branch with the changes was not the one being tested, rather just main, therefore wasting time and resource. With the ticket https://github.com/elastic/security-team/issues/9129 we will solve this issue. But in the meanwhile, we are disabling these jobs. (cherry picked from commit 48283b6) # Conflicts: # .github/workflows/ci.yml
mergify bot
pushed a commit
that referenced
this pull request
Oct 17, 2024
Before this change all the PRs were executing these long running jobs, on avg ~15min each run. But the branch with the changes was not the one being tested, rather just main, therefore wasting time and resource. With the ticket https://github.com/elastic/security-team/issues/9129 we will solve this issue. But in the meanwhile, we are disabling these jobs. (cherry picked from commit 48283b6) # Conflicts: # .github/workflows/ci.yml
This was referenced Oct 17, 2024
mergify bot
pushed a commit
that referenced
this pull request
Oct 17, 2024
Before this change all the PRs were executing these long running jobs, on avg ~15min each run. But the branch with the changes was not the one being tested, rather just main, therefore wasting time and resource. With the ticket https://github.com/elastic/security-team/issues/9129 we will solve this issue. But in the meanwhile, we are disabling these jobs. (cherry picked from commit 48283b6) # Conflicts: # .github/workflows/ci.yml
mergify bot
pushed a commit
that referenced
this pull request
Oct 17, 2024
Before this change all the PRs were executing these long running jobs, on avg ~15min each run. But the branch with the changes was not the one being tested, rather just main, therefore wasting time and resource. With the ticket https://github.com/elastic/security-team/issues/9129 we will solve this issue. But in the meanwhile, we are disabling these jobs. (cherry picked from commit 48283b6) # Conflicts: # .github/workflows/ci.yml
mergify bot
pushed a commit
that referenced
this pull request
Oct 17, 2024
Before this change all the PRs were executing these long running jobs, on avg ~15min each run. But the branch with the changes was not the one being tested, rather just main, therefore wasting time and resource. With the ticket https://github.com/elastic/security-team/issues/9129 we will solve this issue. But in the meanwhile, we are disabling these jobs. (cherry picked from commit 48283b6) # Conflicts: # .github/workflows/ci.yml
This was referenced Oct 17, 2024
mergify bot
pushed a commit
that referenced
this pull request
Oct 17, 2024
Before this change all the PRs were executing these long running jobs, on avg ~15min each run. But the branch with the changes was not the one being tested, rather just main, therefore wasting time and resource. With the ticket https://github.com/elastic/security-team/issues/9129 we will solve this issue. But in the meanwhile, we are disabling these jobs. (cherry picked from commit 48283b6) # Conflicts: # .github/workflows/ci.yml
mergify bot
pushed a commit
that referenced
this pull request
Oct 17, 2024
Before this change all the PRs were executing these long running jobs, on avg ~15min each run. But the branch with the changes was not the one being tested, rather just main, therefore wasting time and resource. With the ticket https://github.com/elastic/security-team/issues/9129 we will solve this issue. But in the meanwhile, we are disabling these jobs. (cherry picked from commit 48283b6)
mergify bot
pushed a commit
that referenced
this pull request
Oct 17, 2024
Before this change all the PRs were executing these long running jobs, on avg ~15min each run. But the branch with the changes was not the one being tested, rather just main, therefore wasting time and resource. With the ticket https://github.com/elastic/security-team/issues/9129 we will solve this issue. But in the meanwhile, we are disabling these jobs. (cherry picked from commit 48283b6)
This was referenced Oct 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of your changes
Before this change all the PRs were executing these long running jobs, on avg ~15min each run. But the branch with the changes was not the one being tested, rather just main, therefore wasting time and resource. With the ticket https://github.com/elastic/security-team/issues/9129 we will solve this issue. But in the meanwhile, we are disabling these jobs.