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

chore(ci): remove django circleci test suite [backport 2.14] #11222

Merged
merged 2 commits into from
Oct 30, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 30, 2024

Backport c5134f9 from #11220 to 2.14.

Context

Recently, the django test suite on CircleCI has been consistently failing, which has been blocking many PRs. While investigating, we observed:

  • that when we migrated the django test suite to GitLab, we didn't remove it from CircleCI (ci: move django tests from CircleCI to GitLab #10611).
  • we can reproduce the errors we saw on CI when the testagent container isn't spun up locally
  • the django tests fail consistently with python 3.8 for the snapshot tests in CI, but consistently pass when run locally with a testagent (we tried with 64b33747062c585df9f0eb810c28d367379a9998: the head commit on main, 0c17d211b9fac9d7855966f70530f19ed17e27a3 : @avara1986 's original django fix PR, and 127e5b72ee45e55e4c6d9b7d07922d47099483fb: the PR that merged right before @avara1986 's fix PR)

The root cause of the CirlceCI issue is still under investigation, but given that this is currently blocking PRs from merging but the same tests are already running AND passing in GitLab, this PR aims to remove the django test suite from CircleCI to unblock contributors.

@erikayasuda will continue investigating the root cause of the CircleCI issues, but with this PR merged that investigation will not be a blocker.

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

## Context
Recently, the django test suite on CircleCI has been consistently
failing, which has been blocking many PRs. While investigating, we
observed:
- that when we migrated the django test suite to GitLab, we didn't
remove it from CircleCI
(#10611).
- we can reproduce the errors we saw on CI when the testagent container
isn't spun up locally
- the django tests fail consistently with python 3.8 for the snapshot
tests in CI, but consistently pass when run locally with a testagent (we
tried with `64b33747062c585df9f0eb810c28d367379a9998`: the head commit
on `main`, `0c17d211b9fac9d7855966f70530f19ed17e27a3` : @avara1986 's
original django fix PR, and `127e5b72ee45e55e4c6d9b7d07922d47099483fb`:
the PR that merged right before @avara1986 's fix PR)

The root cause of the CirlceCI issue is still under investigation, but
given that this is currently blocking PRs from merging but the same
tests are already running AND passing in GitLab, this PR aims to remove
the django test suite from CircleCI to unblock contributors.

@erikayasuda will continue investigating the root cause of the CircleCI
issues, but with this PR merged that investigation will not be a
blocker.

## Checklist
- [x] 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](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
- The change includes or references documentation updates if necessary
- Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist
- [x] 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](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
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](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)

(cherry picked from commit c5134f9)
@github-actions github-actions bot requested review from a team as code owners October 30, 2024 09:28
@github-actions github-actions bot added the changelog/no-changelog A changelog entry is not required for this PR. label Oct 30, 2024
@datadog-dd-trace-py-rkomorn
Copy link

datadog-dd-trace-py-rkomorn bot commented Oct 30, 2024

Datadog Report

Branch report: backport-11220-to-2.14
Commit report: 1845180
Test service: dd-trace-py

✅ 0 Failed, 592 Passed, 694 Skipped, 21m 15.04s Total duration (17m 50.14s time saved)

@gnufede gnufede closed this Oct 30, 2024
@gnufede gnufede reopened this Oct 30, 2024
@gnufede gnufede enabled auto-merge (squash) October 30, 2024 09:54
Copy link
Contributor Author

CODEOWNERS have been resolved as:

.circleci/config.templ.yml                                              @DataDog/python-guild @DataDog/apm-core-python

@pr-commenter
Copy link

pr-commenter bot commented Oct 30, 2024

Benchmarks

Benchmark execution time: 2024-10-30 15:01:36

Comparing candidate commit 1845180 in PR branch backport-11220-to-2.14 with baseline commit 1b1b85c in branch 2.14.

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

@gnufede gnufede merged commit 572e1f8 into 2.14 Oct 30, 2024
521 checks passed
@gnufede gnufede deleted the backport-11220-to-2.14 branch October 30, 2024 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog A changelog entry is not required for this PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants