Skip to content

Remove test trace #1422

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

Merged
merged 1 commit into from
Jun 6, 2025
Merged

Remove test trace #1422

merged 1 commit into from
Jun 6, 2025

Conversation

AMaini503
Copy link
Contributor

Remove test trace

@AMaini503 AMaini503 requested a review from a team as a code owner June 6, 2025 05:57
@AMaini503 AMaini503 requested a review from pauld-msft June 6, 2025 05:57
Copy link

codecov bot commented Jun 6, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.7%. Comparing base (c2f96db) to head (3bffebb).
Report is 1 commits behind head on main.

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #1422   +/-   ##
=====================================
  Coverage   89.7%   89.7%           
=====================================
  Files        407     407           
  Lines      32380   32379    -1     
  Branches    2000    2000           
=====================================
  Hits       29073   29073           
  Misses      2881    2881           
+ Partials     426     425    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@AMaini503 AMaini503 merged commit 2a41d42 into main Jun 6, 2025
26 checks passed
@AMaini503 AMaini503 deleted the user/aamaini/2287154 branch June 6, 2025 06:14
Copy link

github-actions bot commented Jun 6, 2025

👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:

  • The detector detects more or fewer components than before
  • The detector generates different parent/child graph relationships than before
  • The detector generates different devDependencies values than before

If none of the above scenarios apply, feel free to ignore this comment 🙂

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.

2 participants