Skip to content

ci: install the scheduled drift check with pip; close the probe issue when probes recover - #488

Merged
enriquea merged 1 commit into
devfrom
ci/drift-runner-install
Nov 18, 2026
Merged

enriquea merged 1 commit into
devfrom
ci/drift-runner-install

Conversation

@enriquea

Copy link
Copy Markdown
Member

Summary

  • Scheduled drift check (drift.yml): ubuntu-latest is now 26.04, which ships no conda, so $CONDA is unset and conda env update exits 127 before any probe runs. The 2026-11-15 run failed this way, and no drift PR has been opened since. The probes and drift_to_pr.py need nothing conda provides, so the job now installs the way drift-health.yml does (setup-python + requirements.txt + .[ptm]). drift-health.yml already runs the same probes on the same runner successfully.
  • Probe health (drift-health.yml): the job opened or commented on the drift:probe-failed issue 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.yml with dry_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.

… 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.
@qodo-code-review

Copy link
Copy Markdown
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

@coderabbitai

coderabbitai Bot commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: a2e39b87-c235-4c69-ab64-f9269ec21880

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@enriquea
enriquea merged commit 21af222 into dev Nov 18, 2026
11 checks passed
@enriquea
enriquea deleted the ci/drift-runner-install branch November 18, 2026 20:49
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.

1 participant