You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This means that if you've built the implementations locally, the binaries will be synced to the server as well. Apparently, these binaries aren't overwritten by the build process, leading to inconsistent state. And, if you're building on a different architecture, those binaries can't be executed.
Possible solutions: Be more careful what to sync to the server. One way to do that could be obtaining the list of files tracked by Git, and only syncing those. Or alternatively, exclude the files ignored by Git, or at the very least blacklist the build outputs.
The text was updated successfully, but these errors were encountered:
marten-seemann
changed the title
perf: runner setup is brittle
perf: rsync everything is brittle
Sep 7, 2023
The runner syncs the current state of the directory to the EC2 instances:
test-plans/perf/runner/src/index.ts
Lines 217 to 218 in 0b4e5e4
This means that if you've built the implementations locally, the binaries will be synced to the server as well. Apparently, these binaries aren't overwritten by the build process, leading to inconsistent state. And, if you're building on a different architecture, those binaries can't be executed.
Possible solutions: Be more careful what to sync to the server. One way to do that could be obtaining the list of files tracked by Git, and only syncing those. Or alternatively, exclude the files ignored by Git, or at the very least blacklist the build outputs.
The text was updated successfully, but these errors were encountered: