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

tests: fix check to enable the race detector in supported platforms #40764

Merged
merged 5 commits into from
Sep 16, 2024

Conversation

mauri870
Copy link
Member

@mauri870 mauri870 commented Sep 11, 2024

Proposed commit message

This code is almost 4 years old, the support for the race detector was
lacking at that point and Elastic had its first steps with arm64 builds of Beats.

I updated the check to allow tests to run with RACE_DETECTOR=1 in supported
platforms, this includes linux/arm64 and darwin/arm64.

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.

How to test this PR locally

Try running tests on arm64 platforms with RACE_DETECTOR=1

This code is almost 4 years old, the support for the race detector was
lacking at that point and Elastic had its first steps with arm64 builds of Beats.

I updated the check to allow tests to run with RACE_DETECTOR=true in supported
platforms, this includes linux/arm64 and darwin/arm64.
@mauri870 mauri870 added cleanup Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Sep 11, 2024
@mauri870 mauri870 requested a review from a team as a code owner September 11, 2024 16:06
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Sep 11, 2024
Copy link
Contributor

mergify bot commented Sep 11, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @mauri870? 🙏.
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-8./d is the label to automatically backport to the 8./d branch. /d is the digit

Copy link
Contributor

mergify bot commented Sep 11, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Sep 11, 2024
@mauri870 mauri870 added backport-skip Skip notification from the automated backport with mergify and removed backport-8.x Automated backport to the 8.x branch with mergify labels Sep 12, 2024
@mauri870 mauri870 enabled auto-merge (squash) September 16, 2024 10:59
@mauri870 mauri870 merged commit a4387db into elastic:main Sep 16, 2024
125 checks passed
@pierrehilbert
Copy link
Collaborator

@mauri870 any reason why we are not backporting this to 8.x branch?

@mauri870
Copy link
Member Author

@mauri870 any reason why we are not backporting this to 8.x branch?

I think I should clarify what is worth backporting. This is a minor change to support RACE on arm64, not a bug fix or anything significant enough to justify backporting, so I added the skip-backport label.

@mauri870
Copy link
Member Author

@pierrehilbert Should I open a backport PR to 8.x manually?

@pierrehilbert
Copy link
Collaborator

I think this is something we could use in 8.x branches too but I don't have strong opinion here, more difficult for me to find reason not to backport it.

@mauri870 mauri870 added backport-8.x Automated backport to the 8.x branch with mergify and removed backport-skip Skip notification from the automated backport with mergify labels Sep 16, 2024
mergify bot pushed a commit that referenced this pull request Sep 16, 2024
…40764)

* tests: fix check to enable the race detector in supported platforms

This code is almost 4 years old, the support for the race detector was
lacking at that point and Elastic had its first steps with arm64 builds of Beats.

I updated the check to allow tests to run with RACE_DETECTOR=true in supported
platforms, this includes linux/arm64 and darwin/arm64.

* add log if race is enabled for an unsupported platform

(cherry picked from commit a4387db)
pierrehilbert pushed a commit that referenced this pull request Sep 17, 2024
…40764) (#40847)

* tests: fix check to enable the race detector in supported platforms

This code is almost 4 years old, the support for the race detector was
lacking at that point and Elastic had its first steps with arm64 builds of Beats.

I updated the check to allow tests to run with RACE_DETECTOR=true in supported
platforms, this includes linux/arm64 and darwin/arm64.

* add log if race is enabled for an unsupported platform

(cherry picked from commit a4387db)

Co-authored-by: Mauri de Souza Meneguzzo <mauri870@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify cleanup Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants