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

fix: Standardize architectures #249

Merged
merged 1 commit into from
May 2, 2024
Merged

Conversation

fuzzybinary
Copy link
Member

What does this PR do?

The symbolication service currently understands arm, arm64, x86 and x64 as valid symbol file architectures. Instead of adding the Android ABIs, we map them to those architectures instead.

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Make sure you discussed the feature or bugfix with the maintaining team in an Issue
  • Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

@fuzzybinary fuzzybinary requested review from a team as code owners April 19, 2024 20:20
Comment on lines +85 to +90
internal val SUPPORTED_ARCHS = setOf(
SupportedArchitectureMapping("armeabi-v7a", "arm"),
SupportedArchitectureMapping("arm64-v8a", "arm64"),
SupportedArchitectureMapping("x86", "x86"),
SupportedArchitectureMapping("x86_64", "x64")
)
Copy link
Member

Choose a reason for hiding this comment

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

Sounds like could be simply mapOf<String, String>, without introducing data class. But not a big deal.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, I was curious about that. I could go either way but I figured the data class was more descriptive.

Copy link
Member

Choose a reason for hiding this comment

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

just lookup is now linear instead of O(1), but it doesn't really matter here

@fuzzybinary fuzzybinary force-pushed the jward/standardize-arch branch from 1773de1 to 5764026 Compare April 22, 2024 13:31
The symbolication service currently understands `arm`, `arm64`, `x86` and `x64` as valid symbol file architectures. Instead of adding the Android ABIs, we map them to those architectures instead.
@fuzzybinary fuzzybinary force-pushed the jward/standardize-arch branch from 5764026 to bb01f6f Compare April 22, 2024 18:02
@codecov-commenter
Copy link

Codecov Report

Merging #249 (bb01f6f) into develop (81aace0) will increase coverage by 0.43%.
The diff coverage is 90.91%.

Additional details and impacted files
@@              Coverage Diff              @@
##             develop     #249      +/-   ##
=============================================
+ Coverage      81.30%   81.73%   +0.43%     
- Complexity       203      205       +2     
=============================================
  Files             26       26              
  Lines            802      810       +8     
  Branches         104      104              
=============================================
+ Hits             652      662      +10     
  Misses           112      112              
+ Partials          38       36       -2     
Files Coverage Δ
...datadog/gradle/plugin/DdNdkSymbolFileUploadTask.kt 77.63% <90.91%> (+2.63%) ⬆️

... and 2 files with indirect coverage changes

@fuzzybinary fuzzybinary merged commit 0d00717 into develop May 2, 2024
13 checks passed
@fuzzybinary fuzzybinary deleted the jward/standardize-arch branch May 2, 2024 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants