[Bug 270520] audio/logitechmediaserver: does not install

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270520

--- Comment #10 from Trenton Schulz <trueos@norwegianrockcat.com> ---
(In reply to guido from comment #9)

OK, thanks for the build log.

It looks like there is a test failing in IOInterface module. The relevant parts
from your build script:

PERL_DL_NONLAZY=1 "/usr/local/bin/perl" "-MExtUtils::Command::MM"
"-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0,
'blib/lib', 'blib/arch')" t/*.t
t/basic.t ... 
t/basic.t ... 1/5 

t/basic.t ... ok
t/simple.t .. 
t/simple.t .. 1/11 Address is not in the AF_INET family.
# Looks like your test exited with 255 just after 7.


t/simple.t .. Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 4/11 subtests 

Test Summary Report
-------------------
t/simple.t (Wstat: 65280 Tests: 7 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 11 tests but ran 7.
Files=2, Tests=12,  1 wallclock secs ( 0.02 usr  0.00 sys +  0.05 cusr  0.01
csys =  0.09 CPU)
Result: FAIL
Failed 1/2 test programs. 0/12 subtests failed.
gmake[2]: *** [Makefile:1026: test_dynamic] Error 255


But then the script returns OK, and we proceed to stage an incomplete build.

What is the test that fails? It's testing if loopback has an address of
127.0.0.1

ok($loopback->address eq '127.0.0.1','loopback address');

If you do something different with your loopback that is why the test fails.
Does this provide any insight?

In the meantime, if you want to have a completed build, I'd suggest checking if
loopback is configured as expected or running make config and disable the TEST
option for now. (I have verified that TEST disabled completes as expected, of
course your mileage may vary.)

I will investigate why test failures result in a build success instead of a
build error.

So, there still is a bug that needs to be fixed here (test failures don't stop
the build), but it appears that it might be a configuration issue on your side.

Hope this helps.

-- 
You are receiving this mail because:
You are the assignee for the bug.