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
Not OK: perl 5.18.2 +RC4 on cygwin-thread-multi-64int 1.7.25(0.27053) report 5.18.2-RC4 on cygwin (32bits) #13508
Comments
From sgtmadpm@gmail.comThis is a build failure report for perl from sgtmadpm@gmail.com, This is the result of building perl 5.18.2-RC4 on cygwin 32 bits. Note that Devel::CallChecker on CPAN does work but does not pass tests Failed 4 tests out of 2340, 99.83% okay. Flags: Site configuration information for perl 5.18.2: Configured by stephan at Sat Jan 4 13:33:15 CET 2014. Summary of my perl5 (revision 5 version 18 subversion 2) configuration: Locally applied patches: @INC for perl 5.18.2: Environment for perl 5.18.2: |
From @jkeenanOn 1/5/14 8:21 PM, (via RT) wrote:
Were you able to build perl on this configuration with 5.18.0 or 5.18.1? If not, do you know when you were last able to build perl successfully
Thank you very much. |
The RT System itself - Status changed from 'new' to 'open' |
From @rurbanOn Mon, Jan 6, 2014 at 5:38 PM, James E Keenan <jkeen@verizon.net> wrote:
3 of these always failed. -- |
From sgtmadpm@gmail.comOn Tue, Jan 7, 2014 at 12:38 AM, James E Keenan via RT
Not at 100%.
see my answer below.
Hi Jim, IIRC BinGOS mentioned a bit before 5.18.2-RC1 a 100% build of the 5.18.x I have seen Reini's message but I don't agree completely ;). In my dists I got Anyway I did run prove -v on the failing tests. File/stat.t passes all tests but overall returns a non-0 code shm.t SIGSYS right at the start. Weird considering configure probes taint.t Bails out at 2/3 of the tests. And there is a (ess. empty) callchecker No opinion. I suppose it's kind of related to Devel::CallChecker. quick summary of my cyg config (see D]) * ld2 g++ wrapper The question is: The good news if that 5.18.2 fails less tests than the two previous versions. I did test 5.18.0 with a lot of extra modules but I found it a bit unstable: hth ----------------------------- DETAILS ------------------------------------- A] failures for dists I have (before 5.18.2) I have quite a few dists but only could find the tests results for recent * perl-5.16.1 Failed 8 tests out of 2268, 99.65% okay. * perl-5.16.3 Failed 9 tests out of 2266, 99.60% okay. note that my perl-5.16.3 now has the latest threads modules and does not fail % stephan@armen (/opt/perl_inst/perl5163_inst/perl-5.16.3/t) % my cygwin1.dll was updated on % stephan@armen (/home/stephan) % so no use to shadow sitelib to try recover the tests ;) would not be the same * finally for 5.18.0 I posted something on perlmonks. lots of test failures. http://www.perlmonks.org/?node_id=1034252 Failed 26 tests out of 2336, 98.89% okay. * 5.18.1 had IIRC 3or4 less failures (of the re*t group), but similar. C] prove -v on failed tests I ran this script: % stephan@armen (/home/stephan) % #!/bin/mksh IFS_DEF=$IFS NL=' cd /opt/perl_inst/perl5182_RC4_inst/perl-5.18.2-RC4/t || { perlbin=/opt/perl5182/bin IFS=$NL; for testline in $list echo "\n---\\/----------------------------------------------------------" # ---\/---------------------------------------------------------- Test Summary Report ../ext/XS-APItest/t/call_checker.t (Wstat: 512 Tests: 0 Failed: 0) ---\/---------------------------------------------------------- Test Summary Report ../lib/File/stat.t (Wstat: 7424 Tests: 5008 Failed: 0) ---\/---------------------------------------------------------- Test Summary Report io/shm.t (Wstat: 22528 Tests: 0 Failed: 0) ---\/---------------------------------------------------------- Test Summary Report op/taint.t (Wstat: 140 Tests: 537 Failed: 0) C] comments on perlbug and cygwin 1] perlbug tries to use sendmail if it finds it. On cygwin the problem % stephan@armen (/home/stephan) % 2] To make a prepared message the incantation is not simple. D] cygwin and cygperl * Cygwin is a un*x(linux) platform on top of windows. cyg32 is the stable A version of cygwin has two components: the version of cygwin1.dll and the % stephan@armen (/home/stephan) % It is important to remember that! as soon as you update the cygwin1.dll then * cygwin's released perl is lagging behind at 5.14.2 and there is not as much * Fork is *weak* on cygwin for one main reason. For it to work a child process Still it is __only a stop-gap measure__ and the dynamic loader will load Note that if you have many perl dists the rebase database is not useful. Another good news is that cyg64 will be much safer as it will be easier to find the bare ld2 I used is: % stephan@armen (/opt/perl_inst/perl5182_inst) % # * After running make on a fresh perl, people? normally do a *quick rebase* I use a script with: find . -type f -name '*.dll' | rebase -v -n -b 0x58000000 -T - Reini's perlrebase is similar and does a bit more. What I really use in my * I have seen code that checks Windows envvars before HOME. * A small note Win32 non-core addons. I usually build them just after core perl. I had some hard time with this. I could not rebuild something I had built * Filesystem weirdos. un*x slashy paths have un*x/POSIX semantics and follow Finally a few comments on my own cygwin install... * Since cygwin 1.7.x my cygwin dist goes into C:\cyg. At some point I % mount * As I bundle the full cygwin dist for use in other machines, I try to separate % stephan@armen (/home/stephan) % Note that I use /pXb /pXd for all dists. There are simply aliases to --------------------------- END DETAILS -------------------------------------- |
From @tonycozOn Sun Jan 05 17:21:49 2014, sgtmadpm@gmail.com wrote:
For shm.t - do you have cygserver running? http://cygwin.com/cygwin-ug-net/using-cygserver.html call-checker.t failing is a known problem (#78502). Tony |
From @tonycozOn Wed Jan 15 14:57:11 2014, tonyc wrote:
I've fixed the skip logic in shm.t so it skips properly when Tony |
From @tonycozOn Mon Feb 17 17:02:27 2014, tonyc wrote:
It turned out op/taint.t was dumping core due to SIGSYS from shmget() and msgget() when it attempted to check the tainted of data moved through these mechanisms. I've added signal handlers to catch these and skip the tests as 3383030. Tony |
Migrated from rt.perl.org#120936 (status was 'open')
Searchable as RT120936$
The text was updated successfully, but these errors were encountered: