Skip to content
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

Open
haytham-salhi opened this issue Apr 2, 2016 · 13 comments

Comments

@haytham-salhi
Copy link

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.

@yzhdanov
Copy link
Contributor

yzhdanov commented Apr 4, 2016

Can you please zip the whole directory with all produced output - logs & results - and share it somehow.

Thanks!

@haytham-salhi
Copy link
Author

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.
Waiting for your investigation.

issue_results

@haytham-salhi haytham-salhi reopened this Apr 4, 2016
@yzhdanov
Copy link
Contributor

yzhdanov commented Apr 5, 2016

Thanks! We will try reproducing it and come back to you with our findings.

@haytham-salhi
Copy link
Author

Hello,

Any updates?

@ntikhonov
Copy link

ntikhonov commented Apr 21, 2016

Hi @haytham-salhi !
I've tested yardstick on windows 10 and it works fine, the results folders have been created. Please, pay your attention that results folders will be created in current directory, not root yardstick directory.

Please let me know if it works for you.

@haytham-salhi
Copy link
Author

Hi @ntikhonov

I tried it on Windows 10. Still no luck though. Here is the console output when running the drivers:

Haytham@DESKTOP-NABF4QC /cygdrive/c/MarsProjects/git/distributedproject/Distribu tedCachingPerformanceAnalysis $ ./bin/benchmark-manual-drivers-start.bat <01:40:39><yardstick> Using default properties file: config\benchmark-win.proper ties <01:40:39><yardstick> Starting driver config '--outputFolder results-20160426-01 4039 --localBind 127.0.0.1 --port 1234 -d 30 -t 1 -dn HazelcastDriverBenchmark - sn HazelcastServer -ds haytham-salhi-description_2' <01:40:39><yardstick> Log file: C:\MarsProjects\git\distributedproject\Distribut edCachingPerformanceAnalysis\bin\..\logs-20160426-014039\logs_drivers\0_driver.l og <01:40:39><yardstick> Driver is started <01:40:39><yardstick> Driver is stopped <01:40:39><yardstick> Starting driver config '--outputFolder results-20160426-01 4039 --localBind 127.0.0.1 --port 1234 -d 30 -t 2 -dn HazelcastDriverBenchmark - sn HazelcastServer -ds haytham-salhi-description_4' <01:40:39><yardstick> Log file: C:\MarsProjects\git\distributedproject\Distribut edCachingPerformanceAnalysis\bin\..\logs-20160426-014039\logs_drivers\1_driver.l og <01:40:39><yardstick> Driver is started <01:40:39><yardstick> Driver is stopped <01:42:31><yardstick> All drivers are stopped

The logs folder are generated but the output folders mentioned above are no generated!!

@agoncharuk
Copy link
Contributor

@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.

@haytham-salhi
Copy link
Author

@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!!

@ntikhonov
Copy link

ntikhonov commented Apr 26, 2016

@haytham-salhi Could you try to use yardstick from PowerShell (without cigwin)?

@haytham-salhi
Copy link
Author

haytham-salhi commented Apr 27, 2016

@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!
capture

@ntikhonov
Copy link

@haytham-salhi Did you look at bin folder? Could you please execute ls command after benchmark stopped?

@yzhdanov
Copy link
Contributor

I suppose it is "dir" command for Windows.

@haytham-salhi
Copy link
Author

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants