Config error Permission denied: running existing jmx through yaml

202 views
Skip to first unread message

Vin

unread,
Apr 21, 2017, 11:23:19 AM4/21/17
to codename-taurus
Trying to run an existing jmx file through yaml, code as under:
execution:
- iteration: 1
  scenario: with_script


scenarios:
 with_script:
  script: C:/pathToJMeterScript/File1.jmx

Executing from command line under my home directory:  bzt C:\path\YamlFile.yml
Following error is showing up:
11:04:42 ERROR: Config Error: Error when reading config file 'C:\path': [Errno
13] Permission denied: 'C:\\path'

I'm in my early stage with Taurus...:)
Thx.
-Vin

Andrey Pokhilko

unread,
Apr 21, 2017, 11:41:30 AM4/21/17
to codenam...@googlegroups.com

Hi,

Try moving all files under your home directory. This is OS level message...


Andrey Pohilko
Chief Scientist
P: +7 (909) 631-21-69
BlazeMeter Inc.
--
You received this message because you are subscribed to the Google Groups "codename-taurus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codename-taur...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codename-taurus/62c4da32-f732-4e4b-8f28-929b259757e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Vin

unread,
Apr 21, 2017, 12:11:51 PM4/21/17
to codename-taurus, andrey....@contractor.ca.com
Couple of days ago, when I started with Taurus, I ran one simple test & it ran without any error.
I ran from home & gave the path to the yaml file.
Not sure why it will not run now.
Also, conceptually it doesn't seem correct that I keep the scripts to the home directory. I mean the scripts should reside in any structure that's suitable to the design.


Vin

unread,
Apr 21, 2017, 12:33:51 PM4/21/17
to codename-taurus, andrey....@contractor.ca.com
Figured out...was running from Home, while earlier, I ran it from the the path where the script resided.

Andrey Pokhilko

unread,
Apr 21, 2017, 12:43:27 PM4/21/17
to Vin, codename-taurus

I understand what happens. By default, Taurus creates artifacts dir in current directory. You can configure it to be in some fixed writable location, so it won't matter where you are when running it.


Andrey Pohilko
Chief Scientist
P: +7 (909) 631-21-69
BlazeMeter Inc.
Reply all
Reply to author
Forward
0 new messages