Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Option 'feature-debug-profile' was already defined

Open
#223 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
perl
Domain
testing-qa

Research direction

Reproduce the failure with the shown PERL_DL_NONLAZY command and test.pl. Read App/Yath.pm around line 121 and App/Yath/Plugin/Feature.pm around line 106 to trace why feature-debug-profile is defined twice. Done means the affected test suite completes without the duplicate-option error.

Written by the indexing model from the issue text.

Description

On some of my smokers the test suite fails (seen with Test2-Harness-1.000050, but also with older versions):

PERL_DL_NONLAZY=1 "/usr/perl5.24.1p/bin/perl" "-Iblib/lib" "-Iblib/arch" test.pl
1..2
Option 'feature-debug-profile' was already defined (/usr/perl5.24.1p/lib/site_perl/5.24.1/App/Yath/Plugin/Feature.pm line 106) at /home/cpansand/.cpan/build/2021042719/Test2-Harness-1.000050-0/lib/App/Yath.pm line 121.
BEGIN failed--compilation aborted at /home/cpansand/.cpan/build/2021042719/Test2-Harness-1.000050-0/scripts/yath line 253.
Option 'feature-debug-profile' was already defined (/usr/perl5.24.1p/lib/site_perl/5.24.1/App/Yath/Plugin/Feature.pm line 106) at /home/cpansand/.cpan/build/2021042719/Test2-Harness-1.000050-0/lib/App/Yath.pm line 121.
BEGIN failed--compilation aborted at /home/cpansand/.cpan/build/2021042719/Test2-Harness-1.000050-0/scripts/yath line 253.
yath exited with 65280yath exited with 65280not ok 1 - Passed tests when run by yath (allow fork)
not ok 2 - Passed tests when run by yath (no fork)
*** Error code 255
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

  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.

More from Test-More/Test2-Harness

All issues in Test-More/Test2-Harness

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.