Flag `--bug-report-dir` does not ensure a unique destination for bug reports
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by tracing the --bug-report-dir entry point and the bug_report fixture, especially add_file_contents and the test-id-to-filename handling shown in the examples. Reproduce the reported cases and inspect the existing tests around bug-report generation. Done means separate reports do not overwrite one another and generated names no longer retain the closing ] character.
Written by the indexing model from the issue text.
Description
Consider
from pathlib import Path
class Test1:
def test(self, bug_report):
bug_report.add_file_contents('test1', Path('test1'))
class Test2:
def test(self, bug_report):
bug_report.add_file_contents('test2', Path('test2'))
When the test is run with --bug-report-dir bug-reports specified, the resulting tree is:
bug-reports
└── test.tar
Also, when the test id is processed to get the file name for the bug report, the closing ] is not removed:
/tmp/pytest-of-ttoth/pytest-current
...
├── test_execute_account_nonexiste0 [123/4549]
│ ├── kprint
│ └── test_execute
│ └── account-nonexistent].tar
├── test_execute_account_nonexistecurrent -> /tmp/pytest-of-ttoth/pytest-39/test_execute_account_nonexiste0
├── test_execute_branch_0
│ ├── kprint
│ └── test_execute
│ └── branch].tar
├── test_execute_branch_current -> /tmp/pytest-of-ttoth/pytest-39/test_execute_branch_0
├── test_execute_step_1_0
│ ├── kprint
│ └── test_execute
│ └── step-1].tar
├── test_execute_step_1_current -> /tmp/pytest-of-ttoth/pytest-39/test_execute_step_1_0
├── test_execute_step_2_0
│ ├── kprint
│ └── test_execute
│ └── step-2].tar
...
- Dominant language
- Python
- Stars
- 591
- Forks
- 163
- PR merge metrics
- No merged PRs in 30d
Contributor 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 runtimeverification/k
-
runtimeverification/k#4939 · 1 assignee ·
-
Concolic Explorer Open
Difficulty 5/5 Over a week Newbie friendliness 32/100
runtimeverification/k#4937 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
runtimeverification/k#4936 ·
-
type:epic
runtimeverification/k#4934 · 4 comments · 1 assignee ·
-
runtimeverification/k#4924 · 1 assignee ·
All issues in runtimeverification/k
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100