Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented May 8, 2025

Backport

This will backport the following commits from master to LatencyTest:

Questions ?

Please refer to the Backport tool documentation

If the node install was installed locally previously the script would
not pick that up and try to install again. It would fail because the
directory already exists and then the path would not get properly setup
for the local install of node.
This change sets PATH to point to the local install anyway. If it doesn't
exist it doesn't matter, if it does exist we use the local install.

(cherry picked from commit 00aaa52)
@github-actions github-actions bot merged commit a3890f7 into LatencyTest May 8, 2025
@changeset-bot
Copy link

changeset-bot bot commented May 8, 2025

⚠️ No Changeset found

Latest commit: d80e7ec

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@mcottontensor mcottontensor deleted the backport/LatencyTest/pr-611 branch May 8, 2025 07:10
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.

2 participants