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

[anza migration]: fix download path for cluster test #204

Merged
merged 1 commit into from
Mar 12, 2024

Conversation

yihau
Copy link
Member

@yihau yihau commented Mar 12, 2024

Problem

missed some links

Summary of Changes

update them to anza

@yihau yihau requested review from willhickey and joeaba March 12, 2024 09:34
@yihau yihau added the automerge automerge Merge this Pull Request automatically once CI passes label Mar 12, 2024
@mergify mergify bot merged commit 2078153 into anza-xyz:master Mar 12, 2024
17 checks passed
@yihau yihau deleted the fix-system-perf-test branch March 13, 2024 04:07
@yihau yihau added the v1.17 label Mar 27, 2024
@yihau
Copy link
Member Author

yihau commented Mar 27, 2024

used this PR to test branch rule

Copy link

mergify bot commented Mar 27, 2024

Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule.

mergify bot pushed a commit that referenced this pull request Mar 27, 2024
(cherry picked from commit 2078153)

# Conflicts:
#	net/net.sh
#	scripts/agave-install-deploy.sh
@yihau yihau added the v1.18 label Mar 27, 2024
Copy link

mergify bot commented Mar 27, 2024

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.

mergify bot pushed a commit that referenced this pull request Mar 27, 2024
(cherry picked from commit 2078153)

# Conflicts:
#	net/net.sh
#	scripts/agave-install-deploy.sh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge automerge Merge this Pull Request automatically once CI passes v1.18
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants