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

ci: remove DD metrics reporting from CI #10930

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

mujahidkay
Copy link
Member

@mujahidkay mujahidkay commented Feb 3, 2025

Apparently, our contract with DD run till September. Pending confirmation, this PR will remain draft. Integration test and benchmark results DO NOT get reported GCP right now. Ideally, we should only merge this when we handle these two but not a hard requirement IMO.

closes: ticket

Description

Removes all Datadog related integration for reporting unit test metrics. Also removes additional helper scripts. We are not removing integration test and benchmark test metric reporting right now - that will be done once those metrics are exported to GCP.

Security Considerations

None

Scaling Considerations

None

Documentation Considerations

Its CI only so None

Testing Considerations

all CI.

Upgrade Considerations

None

@mujahidkay mujahidkay self-assigned this Feb 3, 2025
Copy link

cloudflare-workers-and-pages bot commented Feb 3, 2025

Deploying agoric-sdk with  Cloudflare Pages  Cloudflare Pages

Latest commit: 8f903f6
Status: ✅  Deploy successful!
Preview URL: https://445a3363.agoric-sdk.pages.dev
Branch Preview URL: https://mk-dd-removal.agoric-sdk.pages.dev

View logs

@mujahidkay mujahidkay added the force:integration Force integration tests to run on PR label Feb 3, 2025
@mujahidkay mujahidkay requested a review from Muneeb147 February 6, 2025 11:32
@Muneeb147
Copy link
Contributor

all CI. Like mentioned in the description, in its current state, we will miss out on benchmark and integration test result metrics because our existing gcp CI reporting script doesn't handle these two cases.

@mujahidkay Do have any engineering issue for it as DD sunset follow-up? Also do you think if it is doable as quick-win then we can sync and work on sending the stats first before stopping the DD reporting.
Test metrics which are currently reported to GCP can be removed from datadog.

@frazarshad Thoughts?

@mujahidkay
Copy link
Member Author

all CI. Like mentioned in the description, in its current state, we will miss out on benchmark and integration test result metrics because our existing gcp CI reporting script doesn't handle these two cases.

@mujahidkay Do have any engineering issue for it as DD sunset follow-up? Also do you think if it is doable as quick-win then we can sync and work on sending the stats first before stopping the DD reporting. Test metrics which are currently reported to GCP can be removed from datadog.

@frazarshad Thoughts?

@Muneeb147 I'm not certain how quick of a win would those be. I'm in favor of benching this PR altogether till we port those metrics to GCP (no harm done AFAIK as our contract runs till September) and hopefully we can get this done in a sprint.
I'm also not opposed to your call of removing everything but integration and benchmark reporting so let's make a call on it, and move forward

@mujahidkay mujahidkay marked this pull request as ready for review February 14, 2025 09:43
@mujahidkay mujahidkay requested a review from a team as a code owner February 14, 2025 09:43
@@ -22,23 +18,6 @@ inputs:
runs:
using: composite
steps:
- name: upload tests
Copy link
Contributor

Choose a reason for hiding this comment

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

@mujahidkay Won't it stop reporting of integration and benchmarking too?

Copy link
Member Author

Choose a reason for hiding this comment

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

This step is used to collect info from individual packages' unit tests via collect-testruns.sh which further converts ava output to a junit format. And each package's junit xml is then exported to DD via

timeout 30 npx @datadog/datadog-ci junit upload --service agoric-sdk ./packages/*/junit.xml

I don't understand why this needs to be done in test-docker-build step. The info is already being sent when we run test-all-packages. On the other hand, benchmarking uses a completely different action which I have kept as is.

Copy link
Member Author

Choose a reason for hiding this comment

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

That being said, would appreciate a second set of eyes on this. Maybe @usmanmani1122 👀

Copy link
Member

@turadg turadg left a comment

Choose a reason for hiding this comment

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

To close out https://github.com/Agoric/product-tasks/issues/236 I think also requires,

  • remove patches/ava+5.3.1.patch that fed timing data to these scripts
  • remove dd-trace dep from agoric-cli
  • (possibly) remove datadog-go dep from golang/cosmos

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
force:integration Force integration tests to run on PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants