Thanks for your experience Chris, I'll try to squeeze in an installation of PDL on one of my virtual servers to see what happens.
Best, Charlie Gonzalez (E) [email protected] Github Profile <https://github.com/itcharlie> On Fri, Aug 24, 2018 at 8:29 AM Chris Marshall <[email protected]> wrote: > I'm not sure the best way to address these issues, but PDL (the Perl Data > Language module) has a large XS/C component with autogenerated code which > needs a lot of memory to build, a working compiler, and often extra time > since if the memory is tight and swap to disk happens then the jobs can > take very long to complete. > > --Chris > > On Thu, Aug 23, 2018 at 10:25 PM Doug Bell <[email protected]> wrote: > >> Hi! Thanks for helping with smoking CPAN modules! >> >> As far as I know, you've set up everything you can correctly. Running a >> tester can be troublesome, as you're finding out. >> >> As for having to hit Enter sometimes, I think that might be related to >> some settings for your CPAN client. You should go into the CPAN shell (type >> "cpan" and hit Enter) and enter the following commands: >> >> o conf auto_commit yes >> - This makes sure that every config change we make next will be >> automatically written >> o conf prerequisites_policy follow >> - This prevents needing to hit "Enter" to install prereqs >> o conf use_prompt_default yes >> - This prevents well-behaved modules from prompting you for input >> o conf halt_on_failure yes >> - This prevents installs from continuing if a prereq is missing >> o conf inactivity_timeout 3600 >> - This causes the CPAN client to wait for an hour for a process to >> complete (including the tests) before giving up on it. The default is 0, >> which means to wait forever >> >> Documentation on these settings can be found here: >> https://perldoc.perl.org/CPAN/FirstTime.html >> >> I do not, myself, run a smoke tester, so if I've got something wrong, the >> long-time testers on this list should hopefully chime in. >> >> Doug Bell >> [email protected] >> >> >> >> On Aug 18, 2018, at 10:43 PM, Charlie Gonzalez <[email protected]> >> wrote: >> >> Hello CPAN Testers, >> >> Today I managed to set up a CPAN Smoke tester running on Windows Server >> 2016 and Strawberry Perl 5.28.0 \o/ YAY!!!, but I did hit a few walls >> trying to get there. >> >> First I want to mention that the CPAN Testers >> <https://qa.perl.org/cpan-testers/> page is concise and to the point. >> This page lead me to the CPAN Testers WIKI <http://wiki.cpantesters.org/> >> from which I went on to learn more about CPAN Testing at the Quick Start >> <http://wiki.cpantesters.org/wiki/QuickStart> page. >> >> Please Note that I am using Google cloud to setup window server >> instances. >> >> In my first attempt, I installed CPAN::Reporter but had run into an issue >> where I was unable to install Data::UUID module ( >> https://github.com/rjbs/Data-UUID/issues/28 ) >> this instance was then deleted due to the fact that I was not able to >> RDP into the box ( The instance was 1 cpu and 3.3 gig ram server ). >> >> In my second attempt, I built another server ( with the same specs as the >> first attempt ) but this time I install CPAN::Reporter::Smoker and had the >> c:\tmp workaround setup that was noted in ( >> https://github.com/rjbs/Data-UUID/issues/24 ). I started the >> CPAN::Reporter::Smoker program but noticed that I didn't have any test >> results sent to metabase ( http://metabase.cpantesters.org/tail/log.txt >> - Thanks to Jim Keenan for this link and the troubleshooting help ). I >> didn't setup my metabase-profile so I found a link to install >> Task-CPAN-Reporter where I could install all of CPAN::Reporter dependencies >> and setup my metabase-profile afterwards. while setting up my >> metabase-profile it turns out I didn't have the proper permission settings >> on the CPAN directory ( >> https://gist.github.com/itcharlie/28d88611e9abae283ccddf39a199832d ). >> after resolving my metabase configuration I was able to start a test >> install of ExtUtils::ModuleMaker >> <https://gist.github.com/itcharlie/b3c9671efc2ab51173e56d817e8d817e> >> and begin the Smoker process again. >> >> Everything was working just fine until I see that my server had hung for >> some reason, I avoided contacting Google for support and moved forward with >> upgrading the hardware to a 2 CPU and 5.5 Gig ram server. Also I sometimes >> have to go to the command prompt and press the enter key while a make is >> running ( sometimes it just hangs there ) >> >> Can anyone in this list recommended specs for a Windows server for CPAN >> Testing? >> >> Any pointers or tips on how I could have done this better I greatly >> appreciate it. >> >> >> Charlie Gonzalez >> (E) [email protected] >> Github Profile <https://github.com/itcharlie> >> >> >>
