Raku / ecosystem-unbitrot

Which modules are not installable?
https://perl6.github.io/ecosystem-unbitrot/
GNU General Public License v3.0
5 stars 4 forks source link

cro #549

Open AlexDaniel opened 5 years ago

AlexDaniel commented 5 years ago

Module cro cannot be installed (AlwaysFail), perhaps it has some failing tests.

If you can't self-assign yourself or attach a label, please let us know on #perl6 channel on freenode or just leave a comment here. We will try to give you privileges as fast as possible.

Output:

===> Searching for: cro
===> Found: cro:ver<0.8.0> [via Zef::Repository::Ecosystems<cpan>]
===> Fetching [OK]: cro:ver<0.8.0> to /home/alex/Blin/data/zef-data/tmp/1549583728.28577.5754/cro-0.8.0.tar.gz
===> Extraction [OK]: cro to /home/alex/Blin/data/zef-data/store/cro-0.8.0.tar.gz
===> Testing: cro:ver<0.8.0>
t/tools-crofile.t ...... ok
# Failed test 'Can add link'
# at t/tools-link-editor.t line 11
# Failed to get the directory contents of '/home/alex/Blin/data/zef-data/store/cro-0.8.0.tar.gz/cro-0.8.0/data/zef/lib': Failed to open dir: No such file or directory
# Looks like you failed 1 test of 8
t/tools-link-editor.t .. 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/8 subtests 
# Check service up attempt 1: connection refused
# Check service up attempt 2: connection refused
# Check service up attempt 3: connection refused
# Check service up attempt 4: connection refused
# Check service up attempt 5: Timed out after 10s
# Check service up attempt 6: connection refused
# Check service up attempt 7: Timed out after 10s
# Check service up attempt 1: Timed out after 10s
t/tools-runner.t ....... ok
t/tools-services.t ..... ok

Test Summary Report
-------------------
t/tools-link-editor.t (Wstat: 256 Tests: 8 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
Files=4, Tests=128, 71 wallclock secs ( 0.06 usr  0.01 sys + 45.26 cusr  1.88 csys = 47.21 CPU)
Result: FAIL
===> Testing [FAIL]: cro:ver<0.8.0>
Failed to get passing tests, but continuing with --force-test
===> Installing: cro:ver<0.8.0>
===> Install [OK] for cro:ver<0.8.0>

1 bin/ script [cro] installed to:
/home/alex/Blin/installed/cro_0.8.0/bin

Ping @croservices

Kaiepi commented 5 years ago

I get different results when I test:

bastille% zef install cro
===> Searching for: cro
===> Searching for missing dependencies: YAMLish, Docker::File, File::Ignore
===> Testing: YAMLish:ver<0.0.5>
===> Testing [OK] for YAMLish:ver<0.0.5>
===> Testing: Docker::File:ver<1.0>:auth<github:jnthn>
===> Testing [OK] for Docker::File:ver<1.0>:auth<github:jnthn>
===> Testing: File::Ignore
===> Testing [OK] for File::Ignore
===> Testing: cro:ver<0.8.0>
# Check service up attempt 1: connection refused
# Check service up attempt 2: connection refused
# Check service up attempt 3: connection refused
# Check service up attempt 4: connection refused
# Check service up attempt 5: connection refused
# Check service up attempt 6: connection refused
# Check service up attempt 7: connection refused
# Check service up attempt 8: connection refused
# Check service up attempt 9: connection refused
# Check service up attempt 10: connection refused
# Check service up attempt 11: connection refused
# Check service up attempt 12: connection refused
# Check service up attempt 13: connection refused
# Check service up attempt 14: connection refused
# Check service up attempt 15: connection refused
# Check service up attempt 16: connection refused
# Check service up attempt 17: connection refused
# Check service up attempt 18: connection refused
# Check service up attempt 19: connection refused
# Check service up attempt 20: connection refused
# Check service up attempt 21: connection refused
# Check service up attempt 22: connection refused
# Check service up attempt 23: connection refused
# Check service up attempt 24: connection refused
# Check service up attempt 25: connection refused
# Check service up attempt 26: connection refused
# Check service up attempt 27: connection refused
# Check service up attempt 28: connection refused
# Check service up attempt 29: connection refused
# Check service up attempt 30: connection refused
# Check service up attempt 31: connection refused
# Check service up attempt 32: connection refused
# Check service up attempt 33: connection refused
# Check service up attempt 34: connection refused
# Check service up attempt 35: connection refused
# Check service up attempt 36: connection refused
# Check service up attempt 37: connection refused
# Check service up attempt 38: connection refused
# Check service up attempt 39: connection refused
# Check service up attempt 40: connection refused
# Failed test 'Could call the started service'
# at t/tools-runner.t line 63
# Failed test 'Got expected resposne from service'
# at t/tools-runner.t line 64
# expected: 'Service 1 OK'
#      got: (Any)

Then the test hangs

Kaiepi commented 5 years ago

t/tools-services-test-dir/service1.p6 is not being run by t/tools-runner.t, but I can't figure out why. I'll leave this to someone else to fix

Altai-man commented 5 years ago

I am afraid that t/tools-runner.t is a known race condition... And there is just not enough manpower to patch Cro issues of this caliber.