Skip to content
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

[7.17] Add required tags to create AWS instances for CI #37717

Merged
merged 3 commits into from
Jan 25, 2024

Conversation

kaiyan-sheng
Copy link
Contributor

Proposed commit message

This PR is to add required tags to create AWS instances for CI.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 23, 2024
@botelastic
Copy link

botelastic bot commented Jan 23, 2024

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 124 min 19 sec

Pipeline error 1

This error is likely related to the pipeline itself. Click here
and then you will see the error (either incorrect syntax or an invalid configuration).

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@elasticmachine
Copy link
Collaborator

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2024-01-24T03:19:11.119+0000

  • Duration: 118 min 53 sec

Test stats 🧪

Test Results
Failed 1
Passed 5593
Skipped 398
Total 5992

Test errors 1

Expand to view the tests failures

Lint / pre-commit / checkjjbb – pre_commit.lint
    Expand to view the error details

     error 
    

    Expand to view the stacktrace

     ![CDATA[- hook id: check-jjbb
    - duration: 5.76s
    - exit code: 1
    
    Transform JJBB to JJB
    Error: Could not open file '.ci/jobs/defaults.yml': Could not find a defaults.yml at specified location
    ]] 
    

Steps errors 5

Expand to view the steps failures

x-pack/filebeat-packaging-linux - mage package
  • Took 9 min 30 sec . View more details here
  • Description: mage package
x-pack/filebeat-packaging-arm-ubuntu-2204-aarch64 - mage package
  • Took 3 min 10 sec . View more details here
  • Description: mage package
x-pack/metricbeat-packaging-linux - mage package
  • Took 12 min 57 sec . View more details here
  • Description: mage package
x-pack/metricbeat-packaging-arm-ubuntu-2204-aarch64 - mage package
  • Took 4 min 48 sec . View more details here
  • Description: mage package
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'hudson.AbortException: script returned exit code 1'

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors 1

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

  • Name: Lint / pre-commit / checkjjbb – pre_commit.lint

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2024-01-25T00:59:59.926+0000

  • Duration: 121 min 57 sec

Test stats 🧪

Test Results
Failed 0
Passed 5594
Skipped 398
Total 5992

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@kaiyan-sheng kaiyan-sheng marked this pull request as ready for review January 25, 2024 03:52
@kaiyan-sheng kaiyan-sheng requested review from a team as code owners January 25, 2024 03:52
@kaiyan-sheng kaiyan-sheng requested review from belimawr and fearful-symmetry and removed request for a team January 25, 2024 03:52
@@ -19,7 +19,7 @@
wipe-workspace: 'True'
name: origin
shallow-clone: true
credentials-id: f6c7695a-671e-4f4f-a331-acdce44ff9ba
credentials-id: github-app-beats-ci
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where does this change come from? :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kaiyan-sheng kaiyan-sheng merged commit cb1769c into elastic:7.17 Jan 25, 2024
39 checks passed
@kaiyan-sheng kaiyan-sheng deleted the fix_aws_7.17 branch January 25, 2024 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants