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
Results folders are not generated on Windows when running the manual scripts #11
Comments
Can you please zip the whole directory with all produced output - logs & results - and share it somehow. Thanks! |
Sure. I've uploaded a compressed folder containing the logs (server and driver), properties file, and the output of console after running the driver. Note that I run it using manual scripts for windows (.bat). Please note as well that you need to change the extension of the attached to zip so that you can unzip it. It fails when trying to upload it as a zip. I don't know why even though it tells you that it accepts .zip!! So I changed the extension to PNG :). Please let me know if you need any further information. |
Thanks! We will try reproducing it and come back to you with our findings. |
Hello, Any updates? |
Hi @haytham-salhi ! Please let me know if it works for you. |
Hi @ntikhonov I tried it on Windows 10. Still no luck though. Here is the console output when running the drivers:
The logs folder are generated but the output folders mentioned above are no generated!! |
@haytham-salhi From the output you provided I see that the driver node is stopped the same second as it was started, which indicates that there is an exception during the driver execution or the driver was not started at all due to invalid config or classpath. Please refer to the full driver logs in the logs folder. |
@agoncharuk That is not right. The logs are generated and the outputs there are normal and do not indicate to any exception. Seems the running script does not print out the time correctly. If you notice the last line, it's 01:42:31, compared to the first line which is 01:40:39, it took about ~ 2 minutes to complete!! |
@haytham-salhi Could you try to use yardstick from PowerShell (without cigwin)? |
@ntikhonov I tried to run it from power shell, still no luck though. Attached is the output. The logs are generated but the results are not! The folder after --outputFolder is not generated! |
@haytham-salhi Did you look at |
I suppose it is "dir" command for Windows. |
@nivanov I'm sure they are not there. I searched whole file system. There is no output foler! I'm wondering where is command in the batch that creates the folder after --outputFolder? |
Hi,
I tried to run the manual scripts (the server and driver) on the *_windows *_and everything went fine. It generates the logs folders and there are no exceptions in the logs. However, at the end of running, the results (output) folders are not generated. Any idea?
P.S: In *_linux *_they are generated properly!
Thank you in advance.
The text was updated successfully, but these errors were encountered: