-
Notifications
You must be signed in to change notification settings - Fork 94
Fix java agent policy #1270
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 java agent policy #1270
Conversation
Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1270 +/- ##
============================================
- Coverage 81.34% 0 -81.35%
============================================
Files 127 0 -127
Lines 5672 0 -5672
Branches 916 0 -916
============================================
- Hits 4614 0 -4614
+ Misses 702 0 -702
+ Partials 356 0 -356 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
harshavamsi have you seen these node connect failures in the past?
|
First time I'm seeing these, given that all PRs with java agent are having the same problem, I no longer think this is flaky. Will need to investigate this. |
that is not true.
agreed that they are not flaky |
Resolved in #1265. |
Description
Fixes java agent build issues
Related Issues
Resolves #[Issue number to be closed when this PR is merged]
Check List
--signoff
.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.