test_pullWithUnnormalizedPath fails in python3 tests.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- git, python
- Domain
- testing-qa
Research direction
Start by running test_pullWithUnnormalizedPath under Python 2 and Python 3, then inspect the traceback in git/config.py, especially release() and write(). Compare the test runner's handling of the logged exception with the final unittest result; done means the Python 3 behavior is explained and the test reports the correct outcome.
Written by the indexing model from the issue text.
Description
For example here
https://circleci.com/gh/box/wavectl/309
The test_pullWithUnnormalizedPath test actually failed. Gave this output:
[test_pullWithUnnormalizedPath.py] ERROR:git.config:Exception during destruction of GitConfigParser
[test_pullWithUnnormalizedPath.py] Traceback (most recent call last):
[test_pullWithUnnormalizedPath.py] File "/home/circleci/project/venv/lib64/python3.6/os.py", line 666, in __getitem__
[test_pullWithUnnormalizedPath.py] value = self._data[self.encodekey(key)]
[test_pullWithUnnormalizedPath.py] KeyError: b'COLUMNS'
[test_pullWithUnnormalizedPath.py]
[test_pullWithUnnormalizedPath.py] During handling of the above exception, another exception occurred:
[test_pullWithUnnormalizedPath.py]
[test_pullWithUnnormalizedPath.py] Traceback (most recent call last):
[test_pullWithUnnormalizedPath.py] File "/home/circleci/project/venv/lib/python3.6/site-packages/git/config.py", line 259, in release
[test_pullWithUnnormalizedPath.py] self.write()
[test_pullWithUnnormalizedPath.py] File "/home/circleci/project/venv/lib/python3.6/site-packages/git/config.py", line 79, in assure_data_present
[test_pullWithUnnormalizedPath.py] return func(self, *args, **kwargs)
[test_pullWithUnnormalizedPath.py] File "/home/circleci/project/venv/lib/python3.6/site-packages/git/config.py", line 488, in write
[test_pullWithUnnormalizedPath.py] with open(self._file_or_files, "wb") as fp:
[test_pullWithUnnormalizedPath.py] FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpxykt9gv0/.git/config'
[test_pullWithUnnormalizedPath.py] .
[test_pullWithUnnormalizedPath.py] ----------------------------------------------------------------------
[test_pullWithUnnormalizedPath.py] Ran 1 test in 3.850s
[test_pullWithUnnormalizedPath.py]
[test_pullWithUnnormalizedPath.py] OK
- Why is this test failing in python3 only. It passes in python2
- Even though there was an exeption, why did the python unittest pass and print this :
[test_pullWithUnnormalizedPath.py] OK?
- Dominant language
- Python
- Stars
- 16
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 box/wavectl
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Add coverage testsOpentestplan
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
testplan
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
tool-calling
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vllm-project/vllm#59838 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
raullenchai/Rapid-MLX#4042 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
transitmatters/mbta-slow-zone-bot#70 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
litestar-org/advanced-alchemy#811 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day