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

Any proxy workload can't run outside DCPerf path with changes on commit f8a35f0ac978ea1fa8d4896394e25fa5aa9b5a3d #39

Open
criscasillas opened this issue Aug 15, 2023 · 0 comments

Comments

@criscasillas
Copy link
Collaborator

Workloads can't be executed outside DCPerf path with changes added on this commit: f8a35f0
Next error comes when you define an absolute path:
[root@meta-spr-tmp4 ~]# /root/DCPerf/benchpress_cli.py run feedsim_default
Loaded 7 benchmarks and 27 jobs
Will run 1 job(s)
Running "feedsim_default": Aggregator like workload. Latency sensitive. Finds maximum QPS that system can sustain while keeping 95th percentile latency <= 500 msecs.

Running setup hooks for "feedsim_default"
Running <benchpress.plugins.hooks.cpu_mpstat.CpuMpstat object at 0x7f1d930d48b0> {'args': ['-u', '1']}
Starting background 'cpu_mpstat' hook: mpstat -u 1
Starting "feedsim_default"
Job execution command: ['./benchmarks/feedsim/run.sh']
"feedsim_default" failed ([Errno 2] No such file or directory: './benchmarks/feedsim/run.sh')
Binary not found, did you forget to install it?
Running cleanup hooks for "feedsim_default"
^CTraceback (most recent call last):
File "/root/DCPerf/benchpress/cli/commands/run.py", line 138, in run
metrics = job.run(args.role, role_in)
File "/root/DCPerf/benchpress/lib/job.py", line 203, in run
process = subprocess.Popen(
File "/usr/lib64/python3.9/subprocess.py", line 951, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib64/python3.9/subprocess.py", line 1821, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: './benchmarks/feedsim/run.sh'

On previous commit 3e8a5a5 This was working with absolute path. But since commit f8a35f0 you need to be inside DCPerf path to successfully execute the workload.

@criscasillas criscasillas changed the title Any proxy workload can run outside DCPerf path with changes on commit f8a35f0ac978ea1fa8d4896394e25fa5aa9b5a3d Any proxy workload can't run outside DCPerf path with changes on commit f8a35f0ac978ea1fa8d4896394e25fa5aa9b5a3d Sep 28, 2023
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

No branches or pull requests

1 participant