Test-More / Test-More/Test2-Harness

"Could not find yath" when using local::lib

Open
#210 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Perl
Stars
28
Forks
30
PR merge metrics
No merged PRs in 30d

Description

We use local::lib style installs extensively for our application. Recently we started using Test2::Harness into local::lib to do our testing. We have ran into an issue when trying to install Test2::Harness::Renderer::JUnit, it uses App::Yath::Util::find_yath for its tests. However, the tests fail because App::Yath::Util::find_yath will not find the local::lib installed yath script since its not in %Config.

Below is an example of how to replicate this. I suspect this is related to https://github.com/cpanel/Test2-Harness-Renderer-JUnit/issues/14 .

> mkdir find_yath_test
> cd find_yath_test/
> cpanm -L local App::Yath::Util
--> Working on App::Yath::Util
...
Building and testing Test2-Harness-1.000042 ... OK
Successfully installed Test2-Harness-1.000042
15 distributions installed
> eval $(perl -Mlocal::lib=local)
> which yath
/.../find_yath_test/local/bin/yath
> perl -MApp::Yath::Util -e 'warn App::Yath::Util::find_yath'
Could not find yath in Config paths at /.../find_yath_test/local/lib/perl5/App/Yath/Util.pm line 52.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the local::lib setup from the issue, then inspect App/Yath/Util.pm around line 52 and the find_yath entry point. Confirm why the local/bin/yath path is absent from the searched Config paths; done means the utility locates that installed yath script and the failing renderer tests pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
perl
Domain
testing-qa
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.