-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add patch for pydantic-core in order to build successfully on CentOS 6 #18303
Conversation
Bloop Bleep... Dogbot HereRegression Detector ResultsRun ID: 748e3006-5566-40b7-9495-ff48e0e0454b ExplanationA regression test is an integrated performance test for Because a target's optimization goal performance in each experiment will vary somewhat each time it is run, we can only estimate mean differences in optimization goal relative to the baseline target. We express these differences as a percentage change relative to the baseline target, denoted "Δ mean %". These estimates are made to a precision that balances accuracy and cost control. We represent this precision as a 90.00% confidence interval denoted "Δ mean % CI": there is a 90.00% chance that the true value of "Δ mean %" is in that interval. We decide whether a change in performance is a "regression" -- a change worth investigating further -- if both of the following two criteria are true:
The table below, if present, lists those experiments that have experienced a statistically significant change in mean optimization goal performance between baseline and comparison SHAs with 90.00% confidence OR have been detected as newly erratic. Negative values of "Δ mean %" mean that baseline is faster, whereas positive values of "Δ mean %" mean that comparison is faster. Results that do not exhibit more than a ±5.00% change in their mean optimization goal are discarded. An experiment is erratic if its coefficient of variation is greater than 0.1. The abbreviated table will be omitted if no interesting change is observed. No interesting changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%. Fine details of change detection per experiment.
|
2358c80
to
07462e4
Compare
7648472
to
cf0b3f1
Compare
e8765c9
to
ff2a403
Compare
ff2a403
to
bb35e20
Compare
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.
🎉
#18303) * Target MUSL when building Rust projects on CentOS 6 * update -core branch * build pydantic-core from source * trigger * Update pydantic-core-build-for-manylinux1.patch * upgrade * Update pydantic-core-build-for-manylinux1.patch * Update pydantic-core-build-for-manylinux1.patch * Update pydantic-core-build-for-manylinux1.patch * Update pydantic-core-build-for-manylinux1.patch * Update pydantic-core-build-for-manylinux1.patch * Update pydantic-core-build-for-manylinux1.patch * Update pydantic-core-build-for-manylinux1.patch * finish * nit * Revert "update -core branch" This reverts commit 0af51e0. * exclude arm * exclude arm * Update .gitlab-ci.yml * Update .gitlab-ci.yml --------- Co-authored-by: Florent Clarret <florent.clarret@datadoghq.com>
Motivation
Fix Pydantic v2 build errors
Requires DataDog/datadog-agent-buildimages#420