Garbled text at the end of a failed test run
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
No source file, test, or entry point is named. Reproduce a failed test run in the vimscript-test-runner, compare the final output with the attached screenshot, and trace where the garbled text is emitted. Done means the failed run ends with readable output and the relevant test or reproduction confirms it.
Written by the indexing model from the issue text.
Description
@kotp, I'm seeing some garbled text at the very end of the test runner output. I'm not sure what I'm looking at, but is this something we need to tweak?
- Dominant language
- Shell
- Stars
- 2
- Forks
- 6
- 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 exercism/vimscript-test-runner
-
x:action/improve x:knowledge/advanced x:module/test-runner x:size/large x:type/coding
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
x:action/improve x:knowledge/advanced x:module/test-runner x:size/large x:type/coding
Difficulty 5/5 Over a week Newbie friendliness 30/100
All issues in exercism/vimscript-test-runner
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
community-scripts/ProxmoxVE#17425 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ll7/robot_sf_ll7#9560 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·