Repository navigation
ci: install the scheduled drift check with pip; close the probe issue when probes recover - #488
Merged
Merged
Conversation
… when probes recover
ubuntu-latest moved to 26.04, which ships no conda: $CONDA is unset and the
drift job's `conda env update` step exits 127 ("command not found") before
any probe runs, so no drift PR has been opened since. The probes and
drift_to_pr.py need nothing conda provides, so the job now installs exactly
as drift-health.yml does (setup-python + requirements.txt + .[ptm]), which
runs the same probes on the same runner.
drift-health.yml opened or commented on the drift:probe-failed issue but
never closed it, so a one-off host outage (insider, ucsc-cellbrowser in #478)
left it open listing probes that had recovered. A run where every probe
passes now closes it.
Contributor
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
drift.yml):ubuntu-latestis now 26.04, which ships no conda, so$CONDAis unset andconda env updateexits 127 before any probe runs. The 2026-11-15 run failed this way, and no drift PR has been opened since. The probes anddrift_to_pr.pyneed nothing conda provides, so the job now installs the waydrift-health.ymldoes (setup-python+requirements.txt+.[ptm]).drift-health.ymlalready runs the same probes on the same runner successfully.drift-health.yml): the job opened or commented on thedrift:probe-failedissue but never closed it, so a brief outage of a source's host (insider, ucsc-cellbrowser in Drift probes failing #478) left the issue open after the probes had recovered. A run where every probe passes now closes it.Verification
Both workflows were dispatched on this branch:
drift.ymlwithdry_run=true(run): installed, probed every dataset, and the helper planned the regenerate/PR steps for the datasets that drifted while the job was broken (clinvar, gencc, clingen, hgnc, uniprot-ptm and others).drift-health.yml(run): every probe passed and the job closed Drift probes failing #478 with its new comment.Scheduled runs use
main, so the fix takes effect after the next dev → main merge.