You might want to check if those steps are applicable for your test case:
http://wiki.cpantesters.org/wiki/SmokeTesting
Em 25/08/2018 14:39, Charlie Gonzalez escreveu:
Hi Alceu,
I run one smoker process on each machine, Here are the virtual machine
specs ( as described by Google Cloud ):
OS : Windows Server 2016
CPU: 2 VCpus - Intel Haswell
Disk: 50 GB - Standard persistent disk
Here's my quick guide to setting up a cpan smoker on Windows ( I going
to place this guide under - "Being a CPAN Tester ->How do I become a
tester? ->Setting up a dedicated Windows test machine" ) :
1- Download and install the version of Strawberry Perl you want to
test ( http://strawberryperl.com/releases.html - I used the
recommended Perl versions in msi edition )
2- create a C:\tmp directory
3- Set permissions to Full control on C:\tmp and C:\Strawberry
4- execute 'cpan' command on a command prompt or powershell terminal (
your preference )
cpan> install Task::CPAN::Reporter
cpan> install CPAN::Reporter::Smoker
cpan> reload cpan
cpan> o conf init test_report
5- open powershell and start the smoker:
perl -MCPAN::Reporter::Smoker -e start
When using the Windows Server OS, the Internet Explorer browser is set
to block any internet content so all you have to do is disable the
"Enhanced Security" in the Internet Explorers settings and proceed
with downloading Strawberry Perl. ( I suspect that Someone using a
Windows Desktop OS will not encounter these issues )
Charlie Gonzalez
(E) itchar...@gmail.com <mailto:itchar...@gmail.com>
Github Profile <https://github.com/itcharlie>
On Sat, Aug 25, 2018 at 12:10 PM Alceu Rodrigues de Freitas Junior via
cpan-testers-discuss <cpan-testers-discuss@perl.org
<mailto:cpan-testers-discuss@perl.org>> wrote:
Em 24/08/2018 23:02, Charlie Gonzalez escreveu:
> Lately, I have been updating a disabled.yml (
>
https://github.com/itcharlie/cpan-testing-configs/blob/master/disabled.yml
> ) file on distros that break while installing them on Strawberry
Perl
> in Windows ( I am not bothering to look at the reasons why the
modules
> are failing to install ).
At least one of the reasons is that doing IPC on Windows sucks big
time.
On UNIX-like OS that is much more reliable (although sometimes I have
the impirical impression that on OpenBSD is slower than compared to
Linux), but on Windows it just fails from time to time without
aparent
reason.
The only sane way to exchange data between two processes over
there is
through sockets.
That being said, I wonder why we don't have something like a "make"
daemon, waiting to receive requests. The processe of doing smoke
tests
involves creating a lot of processes that run ony for a short
period of
time, at least that is what I can see checking OpenBSD with vmstat
during a smoke test (lots of context switch compared to other uses
of CPU).
I'm not saying that this is something easy to fix, far from it. But
maybe it would worth the effort, I guess.
> After upgrading the server instance with 2 virtual cpus and 5.5
gigs
> of ram , google cloud monitoring has stop yelling at me with
> notifications to upgrade the server specs and
CPAN::Reporter::Smoker
> seems to be running a bit quicker now.
5.5GB looks a lot to me, but I'm not playing with Windows and Perl
for a
while nowadays. Are you running multiple smokers at the same time?
You could look for using RAM disks on Windows (not very useful 5
years
back) to store the build_dir content. That should help a bit.
> Since then I have set up 2 more servers to run CPAN tester
reports for
> Perl 5.26 and 5.24 ( I am using this opportunity to learn how its
> done and hash out the steps needed to setup a Smoker on Windows )
>
If you could, it would be great to have your notes on the CPAN
Testers
wiki (http://wiki.cpantesters.org/). :-)
