Re: [multi-mech] Running on Windows7 - ERROR: can not find test script:

[Corey Goldberg]

> Patrick Moran <pjmo...@gmail.com> wrote:
> I'm having trouble getting multimech-run to work on Windows 7.

fwiw, your project ran fine on my machine against local apache.
(Ubuntu 12.04 64 bit, python 2.7.3)

> I've installed the framework by downloading the zip file
> (multi-mechanize-1.2.0) and running python setup.py install (using python
> 2.7) on top of the EPD 7.3 installation.

sounds like it should work, but unfortunately I don't have any windows
machines to try it on myself.

> When I set up simple test I get errors that say the test script cant be
> found.

if you want to dive the code and see where:
"ERROR: can not find test script: a_user.py. aborting user group:" is
coming from, that should give a clue.

here's my output:

----------------
$ multimech-run stressful_test

user_groups: 2
threads: 6

[================100%==================] 30s/30s transactions:
113747 timers: 0 errors: 0



analyzing results...

transactions: 113747
errors: 0

test start: 2012-12-12 13:41:45
test finish: 2012-12-12 13:42:15

created: ./stressful_test/results/results_2012.12.12_13.41.45/results.html

done.
----------------

regards,

-Corey

[Patrick Moran]

It sounds like there is an issue with the script file location on windows only. 

How does multimech find the data scripts? Is there a [config] parameter that can point directly at the scripts versus some default location? I've tried setting the PYTHONPATH, PATH etc and also tried installing the test directory directly off the c:\ drive. I get the same error in all cases. 

There seems to be an internal library that must use a pathname that doesn't translate well between *nix and windows. Do I need to dig through the code?

Thanks,

Pat

On Wednesday, December 12, 2012 1:15:52 PM UTC-5, Patrick Moran wrote:

I'm having trouble getting multimech-run to work on Windows 7. 

I've installed the framework by downloading the zip file (multi-mechanize-1.2.0) and running python setup.py install (using python 2.7) on top of the EPD 7.3 installation.

When I set up simple test I get errors that say the test script cant be found. Here is the output:
---------------- cut here -----------------

C:\>multimech-run stressful_test

  user_groups:  2

  threads: 6

[                  0%                  ]  0s/30s   transactions: 0  timers: 0  e

ERROR: can not find test script: a_user.py.  aborting user group: user_group-2

ERROR: can not find test script: a_user.py.  aborting user group: user_group-2

ERROR: can not find test script: a_user.py.  aborting user group: user_group-2

ERROR: can not find test script: a_user.py.  aborting user group: user_group-1

ERROR: can not find test script: a_user.py.  aborting user group: user_group-1

ERROR: can not find test script: a_user.py.  aborting user group: user_group-1

[=                 3%                  ]  1s/30s   transactions: 0  timers: 0  e

[===               7%                  ]  2s/30s   transactions: 0  timers: 0  e

[====             10%                  ]  3s/30s   transactions: 0  timers: 0  e

[=====            13%                  ]  4s/30s   transactions: 0  timers: 0  e

[======           17%                  ]  5s/30s   transactions: 0  timers: 0  e

[========         20%                  ]  6s/30s   transactions: 0  timers: 0  e

[=========        23%                  ]  7s/30s   transactions: 0  timers: 0  e

[==========       27%                  ]  8s/30s   transactions: 0  timers: 0  e

[==========       27%                  ]  8s/30s

analyzing results...

Traceback (most recent call last):

  File "C:\Python27\Scripts\multimech-run-script.py", line 9, in <module>

    load_entry_point('multi-mechanize==1.2.0', 'console_scripts', 'multimech-run')()

  File "C:\Python27\lib\site-packages\multi_mechanize-1.2.0-py2.7.egg\multimechanize\utilities\run.py", line 64, in main

    run_test()

  File "C:\Python27\lib\site-packages\multi_mechanize-1.2.0-py2.7.egg\multimechanize\utilities\run.py", line 131, in run_test

    results.output_results(output_dir, 'results.csv', run_time, rampup, results_ts_interval, user_group_configs, xml_report)

  File "C:\Python27\lib\site-packages\multi_mechanize-1.2.0-py2.7.egg\multimechanize\results.py", line 19, in output_results

    results = Results(results_dir + results_file, run_time)

  File "C:\Python27\lib\site-packages\multi_mechanize-1.2.0-py2.7.egg\multimechanize\results.py", line 253, in __init__

    self.epoch_start = self.resp_stats_list[0].epoch_secs

IndexError: list index out of range

I've got a directory called stressful_test which is where I put the project. See the zip file for the actual test. I'm running it against a local installation of Apache which is running on localhost

Is there a PATH or other variable I'm missing?

Thanks in advance for your help.

Pat

[Corey Goldberg]

On Wed, Dec 12, 2012 at 2:49 PM, Patrick Moran <pjmo...@gmail.com> wrote:
> Do I need to dig through the code?

I just did.
the script loader is totally rewritten in the current GitHub trunk. I
can't really help debug your current situation (though perhaps try
removing the underscore from the user name) against Multi-mech
v.1.2.0.

could you try the current trunk version instead?

download:
https://github.com/cgoldberg/multi-mechanize/archive/master.zip

unzip and run: python setup.py install

everything should work the same.
please let me know if that helps or not.

-Corey

[Patrick Moran]

Thank you so much... let me try and I will let you know.

Pat

[Patrick Moran]

IT WORKS!!! Thanks!

C:\>multimech-run sc

  user_groups:  2

  threads: 6

[                  0%                  ]  0s/30s   transactions: 0  timers: 0  e

[=                 3%                  ]  1s/30s   transactions: 0  timers: 0  e

[===               7%                  ]  2s/30s   transactions: 0  timers: 0  e

[====             10%                  ]  3s/30s   transactions: 0  timers: 0  e

[=====            13%                  ]  4s/30s   transactions: 4  timers: 4  e

[======           17%                  ]  5s/30s   transactions: 6  timers: 6  e

[========         20%                  ]  6s/30s   transactions: 6  timers: 6  e

[=========        23%                  ]  7s/30s   transactions: 12  timers: 12

[==========       27%                  ]  8s/30s   transactions: 12  timers: 12

[===========      30%                  ]  9s/30s   transactions: 16  timers: 16

[=============    33%                  ]  10s/30s   transactions: 18  timers: 18

[==============   37%                  ]  11s/30s   transactions: 19  timers: 19

[===============  40%                  ]  12s/30s   transactions: 23  timers: 23

[================ 43%                  ]  13s/30s   transactions: 24  timers: 24

[=================47%                  ]  14s/30s   transactions: 27  timers: 27

[=================50%                  ]  15s/30s   transactions: 30  timers: 30

[=================53%                  ]  16s/30s   transactions: 31  timers: 31

[=================57%==                ]  17s/30s   transactions: 35  timers: 35

[=================60%===               ]  18s/30s   transactions: 37  timers: 37

[=================63%====              ]  19s/30s   transactions: 38  timers: 38

[=================67%=====             ]  20s/30s   transactions: 42  timers: 42

[=================70%=======           ]  21s/30s   transactions: 43  timers: 43

[=================73%========          ]  22s/30s   transactions: 46  timers: 46

[=================77%=========         ]  23s/30s   transactions: 49  timers: 49

[=================80%==========        ]  24s/30s   transactions: 52  timers: 52

[=================83%============      ]  25s/30s   transactions: 53  timers: 53

[=================87%=============     ]  26s/30s   transactions: 56  timers: 56

[=================90%==============    ]  27s/30s   transactions: 59  timers: 59

[=================93%===============   ]  28s/30s   transactions: 61  timers: 61

[=================97%================= ]  29s/30s   transactions: 64  timers: 64

[================100%==================]  30s/30s   transactions: 67  timers: 67

[================100%==================]  30s/30s

waiting for all requests to finish...

analyzing results...

transactions: 73

errors: 0

test start: 2012-12-12 16:03:49

test finish: 2012-12-12 16:04:15

created: ./sc/results/results_2012.12.12_16.03.45/results.html

done.

[Arun Das]

What works? What did you try?

On Thursday, 13 December 2012 02:35:47 UTC+5:30, P wrote:

IT WORKS!!! Thanks!

...

[Corey Goldberg]

pip install -e git+http://github.com/cgoldberg/multi-mechanize.git#egg=multimechanize

[Arun Das]

Yes, it does work! :) Thanks for that. When will there be a release with this fix? It's been a while since 1.2.0 :)