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

Enable MacOS M1 stages in the CI on a weekly basis #32173

Merged
merged 6 commits into from
Sep 13, 2022

Conversation

v1v
Copy link
Member

@v1v v1v commented Jun 30, 2022

What does this PR do?

Run build/test in the CI on macos m1 workers. It will run on a weekly basis

Why is it important?

More test coverage

Issues

There are test failures for MacOS M1:

@cmacknz @kpollich , how would you like to proceed? This particular implementation was discussed in an internal issue - you can find it linked to this particular PR with the name configure the required projects to use the new Orka M1 ephemeral workers

@v1v v1v added the macos-m1 Enable stages in the CI for the MacOS M1 label Jun 30, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 30, 2022
@mergify mergify bot assigned v1v Jun 30, 2022
@elasticmachine
Copy link
Collaborator

elasticmachine commented Jun 30, 2022

💔 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

  • Start Time: 2022-09-12T15:59:22.201+0000

  • Duration: 122 min 25 sec

Test stats 🧪

Test Results
Failed 0
Passed 29823
Skipped 2527
Total 32350

Steps errors 6

Expand to view the steps failures

Docker login
  • Took 0 min 15 sec . View more details here
  • Description: set +x if command -v host 2>&1 > /dev/null; then host docker.elastic.co 2>&1 > /dev/null fi if command -v dig 2>&1 > /dev/null; then dig docker.elastic.co 2>&1 > /dev/null fi docker login -u "${DOCKER_USER}" -p "${DOCKER_PASSWORD}" "docker.elastic.co" 2>/dev/null
Terraform Cleanup
  • Took 0 min 1 sec . View more details here
  • Description: .ci/scripts/terraform-cleanup.sh x-pack/filebeat
Terraform Cleanup
  • Took 0 min 1 sec . View more details here
  • Description: .ci/scripts/terraform-cleanup.sh x-pack/filebeat
Terraform Cleanup
  • Took 0 min 0 sec . View more details here
  • Description: .ci/scripts/terraform-cleanup.sh x-pack/metricbeat
Terraform Cleanup
  • Took 0 min 0 sec . View more details here
  • Description: .ci/scripts/terraform-cleanup.sh x-pack/metricbeat
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'hudson.AbortException: script returned exit code 1'

💚 Flaky test report

Tests succeeded.

🤖 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!)

@mtojek mtojek added the Team:Automation Label for the Observability productivity team label Jul 18, 2022
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jul 18, 2022
@mergify
Copy link
Contributor

mergify bot commented Aug 16, 2022

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @v1v? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@mergify
Copy link
Contributor

mergify bot commented Sep 1, 2022

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b feature/support-orka-m1 upstream/feature/support-orka-m1
git merge upstream/main
git push upstream feature/support-orka-m1

@v1v v1v marked this pull request as ready for review September 8, 2022 14:47
@v1v v1v requested review from a team as code owners September 8, 2022 14:47
@v1v v1v requested review from belimawr and leehinman and removed request for a team September 8, 2022 14:47
@v1v
Copy link
Member Author

v1v commented Sep 8, 2022

/test

@v1v v1v requested a review from a team September 8, 2022 15:27
@v1v v1v added the backport-v8.4.0 Automated backport with mergify label Sep 8, 2022
@v1v
Copy link
Member Author

v1v commented Sep 8, 2022

Terraform for MacOS is not available in the existing version (0.13.7) but from https://github.com/hashicorp/terraform/releases/tag/v1.0.2
see https://releases.hashicorp.com/terraform/1.0.2/

Blocked by the bump

@v1v v1v mentioned this pull request Sep 8, 2022
@v1v
Copy link
Member Author

v1v commented Sep 9, 2022

/test

Copy link
Contributor

@belimawr belimawr left a comment

Choose a reason for hiding this comment

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

I'm far from being an expert on our automation, but it seems the "comments" rule should match the Beat name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-v8.4.0 Automated backport with mergify macos-m1 Enable stages in the CI for the MacOS M1 Team:Automation Label for the Observability productivity team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants