`yath --rerun-failed` does not look at default log locaiton
Nobody has claimed this yet.
- #305 by @Koan-Bot — closed without merging
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start by reproducing the commands using yath --rerun-failed and yath --rerun-failed=lastlog.jsonl, then trace the --rerun-failed option handling and its default log selection. Done means the option without an argument reads lastlog.jsonl and reruns only the failed test.
Written by the indexing model from the issue text.
Description
When running yath --rerun-failed I would expect the default log location (lastlog.jsonl) to be assumed, but this does not appear to be true.
To reproduce:
tove:/tmp$ mkdir yath-test
tove:/tmp$ cd yath-test/
tove:/tmp/yath-test$ mkdir t
tove:/tmp/yath-test$ echo "use Test::More; fail('no'); done_testing" > t/1.t
tove:/tmp/yath-test$ echo "use Test::More; pass('yes'); done_testing" > t/2.t
tove:/tmp/yath-test$ echo "use Test::More; pass('yes'); done_testing" > t/3.t
tove:/tmp/yath-test$ yath test -L
Now lastlog.jsonl exists, as a symlink to tmp space.
tove:/tmp/yath-test$ yath --rerun-failed
…and all four tests are run. But I instead I run:
tove:/tmp/yath-test$ yath --rerun-failed=lastlog.jsonl
…then only the failed one is run.
+----------------------------+----------+
| COMPONENT | VERSION |
+----------------------------+----------+
| perl | v5.40.1 |
| App::Yath | 1.000156 |
| Test2::API | 1.302199 |
| Test2::Suite | 0.000162 |
| Test::Builder | 1.302199 |
| App::Yath::Plugin::Cover | 1.000156 |
| App::Yath::Plugin::Git | 1.000156 |
| App::Yath::Plugin::Notify | 1.000156 |
| App::Yath::Plugin::SysInfo | 1.000156 |
| App::Yath::Plugin::YathUI | 1.000156 |
+----------------------------+----------+
- Dominant language
- Perl
- Stars
- 28
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 Test-More/Test2-Harness
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Test-More/Test2-Harness#457 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Test-More/Test2-Harness#450 ·
-
Yath tests don't forward @INC to system commandsMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Test-More/Test2-Harness#296 ·
-
The `t/integration/preload.t` test is broken on riscv64-linux (1.000155)May be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Test-More/Test2-Harness#290 · 3 comments · 2 reactions ·
-
yath displays arbitrary filenames without escapingMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Test-More/Test2-Harness#286 · 1 comment ·
All issues in Test-More/Test2-Harness
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 Under an hour Newbie friendliness 70/100
bioepic-data/bervo#145 · 1 comment ·
Maintainers usually reply within 1 day
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
inverse-inc/packetfence#9413 ·
Maintainers usually reply within 1 day
-
Ubuntu .deb packages ship all files owned by uid/gid 1001 (CI user runner) instead of root:rootOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Help-Wanted Needs-Triage Package-Update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/winget-pkgs#448814 · 1 comment ·
Maintainers usually reply within 1 day