Failure running `run.py`
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- git, python
- Domain
- testing-qa, tooling
Research direction
Reproduce the documented command from run.py, then follow the traceback into regression.py, especially git_checkout and git_command. Investigate the failing git submodule foreach operation and verify that source checkout completes without retries or the pathspec error.
Written by the indexing model from the issue text.
Description
Following the online docs I downloaded and executed the run.py script using
python run.py --runner=Stefan --toolsets=gcc-6.2.1 --tag=develop
which eventually resulted in
# Executing GIT command: /home/stefan/projects/boost_root> git submodule foreach "git submodule deinit ."
Entering 'libs/accumulators'
error: pathspec '.' did not match any file(s) known to git.
Stopping at 'libs/accumulators'; script returned non-zero status.
# git_source_checkout failed with message "GIT command "git submodule foreach "git submodule deinit ."" failed with code 256"
# Retrying (5 more attempts).
...
# Retrying (1 more attempts).
# Executing GIT command: /home/stefan/projects/boost_root> git submodule foreach "git submodule deinit ."
Entering 'libs/accumulators'
error: pathspec '.' did not match any file(s) known to git.
Stopping at 'libs/accumulators'; script returned non-zero status.
# git_source_checkout failed with message "GIT command "git submodule foreach "git submodule deinit ."" failed with code 256"
# Giving up.
Traceback (most recent call last):
File "run.py", line 71, in <module>
runner(root)
File "/home/stefan/projects/boost_regression_src/regression.py", line 287, in __init__
self.main()
File "/home/stefan/projects/boost_regression_src/regression.py", line 624, in main
getattr(self,action_m)()
File "/home/stefan/projects/boost_regression_src/regression.py", line 579, in command_regression
self.command_get_source()
File "/home/stefan/projects/boost_regression_src/regression.py", line 331, in command_get_source
self.retry(self.git_source_checkout)
File "/home/stefan/projects/boost_regression_src/regression.py", line 663, in retry
return f()
File "/home/stefan/projects/boost_regression_src/regression.py", line 876, in git_source_checkout
self.git_checkout(git_info['boost'], self.git_branch(), clean)
File "/home/stefan/projects/boost_regression_src/regression.py", line 847, in git_checkout
self.git_command( 'submodule foreach', 'git submodule deinit .')
File "/home/stefan/projects/boost_regression_src/regression.py", line 835, in git_command
raise Exception( 'GIT command "%s" failed with code %d' % (git_cli, rc) )
Exception: GIT command "git submodule foreach "git submodule deinit ."" failed with code 256
- Dominant language
- C++
- Stars
- 11
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
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.
More from boostorg/regression
-
Server-side regression file processing is fragile and discourages community participation by design. Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
boostorg/regression#68 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
boostorg/regression#51 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
boostorg/regression#47 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
boostorg/regression#44 ·
-
Support python 3 Open
Difficulty 4/5 3-5 days Newbie friendliness 28/100
boostorg/regression#43 · 1 comment ·
All issues in boostorg/regression
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·