Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation breaks with "cpanm Devel::IPerl" #112

Open
Transigence opened this issue Jan 13, 2022 · 4 comments
Open

Installation breaks with "cpanm Devel::IPerl" #112

Transigence opened this issue Jan 13, 2022 · 4 comments

Comments

@Transigence
Copy link

It looks like I cannot install Test::Future::IO::Impl
This is where it all breaks down:

Building and testing Future-IO-0.11
Building Future-IO
t\00use.t ............... ok
t\01sleep.t ............. ok
t\02sysread.t ........... ok
t\03sysread_exactly.t ... ok
t\04syswrite.t .......... ok
t\05syswrite_exactly.t .. ok
connect: The requested address is not valid in its context.
t\06connect.t ........... 
Dubious, test returned 101 (wstat 25856, 0x6500)
No subtests run 
Cannot connect() - connect: The requested address is not valid in its context. at C:\Users\padge\.cpanm\work\1642048950.27276\Future-IO-0.11\blib\lib/Test/Future/IO/Impl.pm line 125.
t\07accept.t ............ 
Dubious, test returned 101 (wstat 25856, 0x6500)
No subtests run 
t\10sleep+sysread.t ..... skipped: Cannot select() on pipes on Windows
t\20impl-override.t ..... ok
t\21impl-before-load.t .. ok
t\99pod.t ............... ok

Windows 10

@mohawk2
Copy link

mohawk2 commented Jan 13, 2022

Shouldn't this be an issue for Test::Future::IO::Impl? What is this distribution supposed to do about it?

@Transigence
Copy link
Author

Yes. I thought of that like five minutes after I posted this. It still may be of use to Devel::IPerl people if others are affected by it.

@zmughal
Copy link
Member

zmughal commented Mar 7, 2022

@leonerd, I'm seeing the same tests failing on CPANTS for MSWin32 and OpenBSD: http://matrix.cpantesters.org/?dist=Future-IO+0.11

@mohawk2
Copy link

mohawk2 commented Mar 9, 2022

Yes. I thought of that like five minutes after I posted this. It still may be of use to Devel::IPerl people if others are affected by it.

It seems to me this repo already has enough open issues that can be fixed within it ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants