Skip to content
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

update telemetry and retarget 25.04 #2569

Merged
merged 3 commits into from
Feb 7, 2025

Conversation

msarahan
Copy link
Contributor

@msarahan msarahan commented Feb 4, 2025

Enables telemetry as a final step in the top-level workflow. See draft docs at rapidsai/docs#568 for more info. Part of https://github.com/rapidsai/build-infra/issues/139

Copy link

copy-pr-bot bot commented Feb 4, 2025

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@msarahan
Copy link
Contributor Author

msarahan commented Feb 4, 2025

/ok to test

@msarahan msarahan added enhancement New feature or request non-breaking Non-breaking change improvement Improvement / enhancement to an existing function labels Feb 4, 2025
@msarahan
Copy link
Contributor Author

msarahan commented Feb 4, 2025

@ajschmidt8 ready for the ENABLE_TELEMETRY variable here

@ajschmidt8
Copy link
Member

@ajschmidt8 ready for the ENABLE_TELEMETRY variable here

done

@msarahan msarahan marked this pull request as ready for review February 6, 2025 15:34
@msarahan msarahan requested a review from a team as a code owner February 6, 2025 15:34
@msarahan msarahan requested a review from bdice February 6, 2025 15:34
@msarahan
Copy link
Contributor Author

msarahan commented Feb 6, 2025

The failure here was a github communication issue with the self-hosted runner: The self-hosted runner: linux-arm64-gpu-a100-latest-1-5g8kz-runner-flssx lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

Shall I try to re-run that job, or request a force merge, so as not to tie up the a100 runner any further?

@ajschmidt8
Copy link
Member

The failure here was a github communication issue with the self-hosted runner: The self-hosted runner: linux-arm64-gpu-a100-latest-1-5g8kz-runner-flssx lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

Shall I try to re-run that job, or request a force merge, so as not to tie up the a100 runner any further?

rerunning is fine

@jameslamb jameslamb removed the request for review from bdice February 7, 2025 21:26
@msarahan
Copy link
Contributor Author

msarahan commented Feb 7, 2025

/merge

@rapids-bot rapids-bot bot merged commit 1aacf2c into rapidsai:branch-25.04 Feb 7, 2025
78 checks passed
@msarahan msarahan deleted the add-telemetry branch February 7, 2025 22:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request improvement Improvement / enhancement to an existing function non-breaking Non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants