RexOps / RexOps/Rex

Rex::Test via prove is broken with 1.5.0

Open
#1,140 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Perl
Stars
737
Forks
214
PR merge metrics
No merged PRs in 30d

Description

Using something like:

REX_USER=user prove -v t/test.t

worked with 1.4.1, but it throws the following error with 1.5.0:

t/test.t .. 
Waiting for SSH to come up on 192.168.122.186:22.
[2017-04-12 11:56:16] ERROR - Error executing task:
[2017-04-12 11:56:16] ERROR - Can't call method "get_opts" on an undefined value at /home/ferki/perl5/perlbrew/perls/perl-5.24/lib/site_perl/5.24.1/Rex/Commands.pm line 1038.

Can't call method "get_opts" on an undefined value at /home/ferki/perl5/perlbrew/perls/perl-5.24/lib/site_perl/5.24.1/Rex/Commands.pm line 1038.
Dubious, test returned 29 (wstat 7424, 0x1d00)
No subtests run 

Test Summary Report
-------------------
t/test.t.t (Wstat: 7424 Tests: 0 Failed: 0)
  Non-zero exit status: 29
  Parse errors: No plan found in TAP output
Files=1, Tests=0, 16 wallclock secs ( 0.02 usr  0.01 sys +  1.62 cusr  1.28 csys =  2.93 CPU)
Result: FAIL

It might be easy to restore this, let's call "unofficial feature" (running rex tests with standard perl testing tools) :)

update: it seems it depends more on the type of tests running, than on the versoin of rex

Contributor guide

Open the contributing guide

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 failure with REX_USER=user prove -v t/test.t, then inspect Rex::Commands.pm around line 1038 and the Rex::Test test entry point. Compare the failing test types and the 1.4.1/1.5.0 behavior; done means the relevant Rex tests run through prove without the undefined get_opts error.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.