microsoft / microsoft/superbenchmark
"No such file or directory" errors when running with --output-dir
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 393
- Forks
- 90
- PR merge metrics
- No merged PRs in 30d
Description
What's the issue, what's expected?:
Running sb run with the optional --output-dir parameter prevents results from being collected from the test nodes, and instead spews No such file or directory errors from the "Synchronize Output Directory" task
How to reproduce it?:
sb run -f config.ini -c default.yaml --output-dir $ALTERNATE_LOCATION
Log message or shapshot?:
TASK [Synchronize Output Directory] ********************************************
fatal: [2.3.1.2]: FAILED! => {"changed": false, "cmd": "/usr/bin/rsync --delay-updates -F --compress --archive --rsh='/usr/bin/ssh -S none -i /Users/lfriedman/.ssh/id_ecdsa -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null' --exclude=nodes --out-format='<<CHANGED>>%i %n%L' ubuntu@2.3.1.2:/var/folders/lt/2k4v_sdd2ljbbl3c4lw538640000gn/T/tmp.QD5dwUu9UM/sb-run/output/ /private/var/folders/lt/2k4v_sdd2ljbbl3c4lw538640000gn/T/tmp.QD5dwUu9UM/sb-run/output/nodes/chimpanzee-1", "msg": "Warning: Permanently added '2.3.1.2' (ED25519) to the list of known hosts.\r\nrsync: [sender] change_dir \"/var/folders/lt/2k4v_sdd2ljbbl3c4lw538640000gn/T/tmp.QD5dwUu9UM/sb-run/output\" failed: No such file or directory (2)\nrsync(80938): warning: receiver has empty file list: exiting\n", "rc": 23}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with sb run -f config.ini -c default.yaml --output-dir $ALTERNATE_LOCATION, then trace the Synchronize Output Directory task and its handling of the output path. Done means results are collected from the test nodes with --output-dir and the task no longer reports No such file or directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100