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
Failed test 'WebSocket closed with status 1009' #1133
Comments
We do automated testing for Windows, this problem does not show up there. https://ci.appveyor.com/project/kraih/mojo |
Closing this issue since no new information has been provided and nobody could verify the problem. |
Actually, looking again, it appears there were similar reports on CPAN Testers. http://www.cpantesters.org/cpan/report/4800d2c3-6e16-1014-885e-f9771f639c1c |
No idea what would cause |
Its happening again: Use of uninitialized value $loop in hash element at /home/Bryan/.cpan/build/Mojolicious-8.32-0/blib/lib/Mojo/UserAgent.pm line 202. |
"Closing this issue since no new information has been provided and nobody could verify the problem." -- I never received any email notifications that there had been any response. As for automated windows testing not showing the problem and like the "CPAN River 3000" project, use of monoculture in coding or testing will limit the errors found. There have been multiple times I've run into errors on core modules on linux that were rejected because I didn't have the same test-environment setup. They didn't wish to have "real world" setups that were different from their clean-room test setup. I know that the windows build and tests are done in a special environment that may not be what people have when they use cpan to download and run tests. Here, even if I did get email, saying it works in a clean-room windows test environment, isn't the same as asking for more information (though I noted the code patch, thank you!).. |
CYGWIN_NT-6.1 Athenae 2.8.2(0.313/5/3) 2017-07-12 10:58 x86_64 Cygwin
Steps to reproduce the behavior
Tried to install latest Mojolicious version:
Expected behavior
no errors
Actual behavior
see above under duplicating -- listed most of the output (pertinent, I think)
I went to the line in question and added print code -- lines with [] , package and line# are my output:
The failing test has an "undef" (the '∄' symbol (There does not exist)) for the req number, the
rest have '1'. I kludged in a '1':
and all tests 'pass'.
My perl version info:
Platform:
osname=cygwin, osvers=2.8.1(0.31253), archname=cygwin-thread-multi
uname='cygwin_nt-6.3 cygwin 2.8.1(0.31253) 2017-07-03 14:11 x86_64 cygwin '
config_args='-des -Dprefix=/usr -Dmksymlinks -Darchname=x86_64-cygwin-threads -Dlibperl=cygperl5_22.dll -Dcc=gcc -Dld=g++ -Accflags=-ggdb -O2 -pipe -Wimplicit-function-declaration -fdebug-prefix-map=/mnt/share/maint/perl.x86_64/build=/usr/src/debug/perl-5.22.4-1 -fdebug-prefix-map=/mnt/share/maint/perl.x86_64/src/perl-5.22.4=/usr/src/debug/perl-5.22.4-1 -fwrapv'
hint=recommended, useposix=true, d_sigaction=define
useithreads=define, usemultiplicity=define
use64bitint=define, use64bitall=define, uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='gcc', ccflags ='-DPERL_USE_SAFE_PUTENV -D_GNU_SOURCE -U__STRICT_ANSI__ -ggdb -O2 -pipe -Wimplicit-function-declaration -fdebug-prefix-map=/mnt/share/maint/perl.x86_64/build=/usr/src/debug/perl-5.22.4-1 -fdebug-prefix-map=/mnt/share/maint/perl.x86_64/src/perl-5.22.4=/usr/src/debug/perl-5.22.4-1 -fwrapv -fno-strict-aliasing -fstack-protector-strong -D_FORTIFY_SOURCE=2',
optimize='-O3',
cppflags='-DPERL_USE_SAFE_PUTENV -D_GNU_SOURCE -U__STRICT_ANSI__ -ggdb -O2 -pipe -Wimplicit-function-declaration -fdebug-prefix-map=/mnt/share/maint/perl.x86_64/build=/usr/src/debug/perl-5.22.4-1 -fdebug-prefix-map=/mnt/share/maint/perl.x86_64/src/perl-5.22.4=/usr/src/debug/perl-5.22.4-1 -fwrapv -fno-strict-aliasing -fstack-protector-strong'
ccversion='', gccversion='5.4.0', gccosandvers=''
intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678, doublekind=3
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16, longdblkind=3
ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries:
ld='g++', ldflags =' -Wl,--enable-auto-import -Wl,--export-all-symbols -Wl,--enable-auto-image-base -fstack-protector-strong'
libpth=/usr/lib
libs=-lpthread -lgdbm -ldb -ldl -lcrypt -lgdbm_compat
perllibs=-lpthread -ldl -lcrypt
libc=/usr/lib/libcygwin.a, so=dll, useshrplib=true, libperl=cygperl5_22.dll
gnulibc_version=''
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=dll, d_dlsymun=undef, ccdlflags=' '
cccdlflags=' ', lddlflags=' --shared -Wl,--enable-auto-import -Wl,--export-all-symbols -Wl,--enable-auto-image-base -fstack-protector-strong'
Characteristics of this binary (from libperl):
Compile-time options: HAS_TIMES MULTIPLICITY PERLIO_LAYERS
PERL_DONT_CREATE_GVSV
PERL_HASH_FUNC_ONE_AT_A_TIME_HARD
PERL_IMPLICIT_CONTEXT PERL_NEW_COPY_ON_WRITE
PERL_PRESERVE_IVUV PERL_USE_SAFE_PUTENV
USE_64_BIT_ALL USE_64_BIT_INT USE_ITHREADS
USE_LARGE_FILES USE_LOCALE USE_LOCALE_COLLATE
USE_LOCALE_CTYPE USE_LOCALE_NUMERIC USE_LOCALE_TIME
USE_PERLIO USE_PERL_ATOF USE_REENTRANT_API
Built under cygwin
Compiled at Jul 15 2017 20:11:53
%ENV:
PERL5LIB=""
PERL5_CPANPLUS_IS_RUNNING="7036"
PERL5_CPAN_IS_RUNNING="7036"
CYGWIN="system nodosfilewarning winsymlinks:native export"
@inc:
/usr/lib/perl5/site_perl/5.22/x86_64-cygwin-threads
/usr/lib/perl5/site_perl/5.22
/usr/lib/perl5/vendor_perl/5.22/x86_64-cygwin-threads
/usr/lib/perl5/vendor_perl/5.22
/usr/lib/perl5/5.22/x86_64-cygwin-threads
/usr/lib/perl5/5.22
.
I didn't know how to examine it further, so am submitting this.
It does happen on repeated builds (for me, anyway), which probably means you won't be able to reproduce it. If you can't -- then just close this for now, as I "kludged around" the problem as shown above...
The text was updated successfully, but these errors were encountered: