-
Notifications
You must be signed in to change notification settings - Fork 222
[BugFix]Remove not using patch_eagle.py for CI. #1385
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
Conversation
6deae75
to
6ee0615
Compare
nice change, approve |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1385 +/- ##
==========================================
- Coverage 27.39% 27.25% -0.14%
==========================================
Files 56 55 -1
Lines 6191 6186 -5
==========================================
- Hits 1696 1686 -10
- Misses 4495 4500 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the removeal of patch code. Thanks! Let's merge once the CI passed
6ee0615
to
0bb3ac1
Compare
this pr need not run long term CI |
50f1ddf
to
874bd3d
Compare
6898fd4
to
d065bdf
Compare
d065bdf
to
85afcf3
Compare
Signed-off-by: yuancaoyaoHW <a2749322671@gmail.com>
85afcf3
to
de5be4e
Compare
What this PR does / why we need it?
This PR aims to address a long-standing CI bug and remove unused code. The specific changes include:
patch_eagle.py
: Deletes thepatch_eagle.py
file, which is no longer utilized by the project. This file was likely legacy code, experimental code, or its functionality has since been replaced by other modules. Its removal helps reduce codebase complexity, improves maintainability, and prevents potential confusion.Does this PR introduce any user-facing change?
No, this PR primarily focuses on internal CI stability maintenance and code cleanup. It does not introduce any user-visible changes to APIs, interfaces, or other behaviors.
How was this patch tested?
CI passed. Specifically:
patch_eagle.py
, it was ensured that any related functional modules (if applicable) continue to work as expected, without introducing new regressions. This was typically verified by running the project's main test suite.