ci: explicitly set resource request/limits for test job

[taegyunkim]

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[github-actions]

CODEOWNERS have been resolved as:

.gitlab/tests.yml                                                       @DataDog/python-guild @DataDog/apm-core-python

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-11-21 04:36:04

Comparing candidate commit 059f0ae in PR branch taegyunkim/ci-resource-limits with baseline commit d5ac5f9 in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 388 metrics, 2 unstable metrics.

[brettlangdon]

would it be better to have a lower request than limit?

most of our jobs aren't going to use 12 CPUs anyways, majority of them are single threaded.

better to have request 1/2 and limit of 12?

same with memory, request of 3/4 and limit of 16?

[brettlangdon]

nvm, based on how the limits are enforced, requests must equal the limit.

I still wonder if this is too aggressive to apply to all of our testrunner jobs, should we be more targeted?

[emmettbutler]

Applying this in a more targeted manner would help reduce resource waste.