Gauge 0.1.8 broken on mac - Incorrect value for runner_request_timeout #222
Comments
|
This warning message is shown if the value of Gauge doesn't fail tests because of the [WARNING] messages. Tests may be failing because of some other error, the whole console output/stack trace would be helpful in debugging this. |
|
Thank you for the reply. I have added both "runner_request_timeout = 10000" and "plugin_connection_timeout = 10000" to my gauge.properties and I see the warnings: "Incorrect value for plugin_kill_timeout in property file.Cannot convert to time" I realize that these are warnings, but the values in my gauge.properties are being ignored. Regardless, the tests all went from passing to failing after upgrading from 0.1.7 to 0.1.8 from a terminal window in OS X. I started IDEA and was able to run the specs no problem. This seemed to correct execution from the command line since I re-ran my previous statement in the terminal window and the spec ran. This is not an ideal fix for our Mac testing VMs that will not IDEA installed. Also, from IDEA the xml-report and html-report plugins generated their output but the following occurs from the command line with no reports being generated: [WARNING] Error starting plugin Html Report 1.0.4. pipe: too many open files I killed orphaned gauge processes before re-running the spec. |
|
Sorry to hear about the issue that you are facing. The one thing that should have changed when you ran the specs from IntelliJ is that it would have recompiled the java files. While running tests on VMs, if you face this issue, just delete the Thanks for reporting the issue that you faced with html-report generation. We will take a look at it. Gauge was not able to generate the xml reports because the xml-report plugin is not installed. You can install it using Regarding |
|
@barrysvee Please make sure you have read access to the gauge.properties file from command-line. The warning you have mentioned happens if Gauge is not able to read the values to certain variables in gauge.properties file. But this would be set to default in case of this problem. |
|
@apoorvam I am able to find gauge.properties under program files in Windows machine. But unable to see this in MAC. Do you have the path where I can find this file in mac? Also how can I set the property file values to default ? |
|
On Mac, the location of properties files depends on how you installed it. If you installed from source or used the .pkg installer, you will find the In case you used homebrew, the file will be in As Apoorva said, the default values are already set in the file. But just for your reference, here they are. |
|
@apoorvam @mahendrakariya Gauge 0.1.7:*Though I have these below warning the specs are running in this gauge version. [WARN] Incorrect value for runner_request_timeout in property file.Cannot convert to time Gauge 0.2.0:*Here specs are not running and I don’t see timeout errors on property file. [INFO] process /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/bin/java with pid 482 quit unexpectedly. exit status 1 |
|
Warnings about timeout values are not fatal, since gauge will internally take the default values. That won't stop the execution. But errors that you got with Gauge 0.2.0 are fatal. Could you please ensure that you have the latest versions of all the plugins? The minimum plugin versions compatible with Gauge 0.2.0 are mentioned in this announcement email. In case you have older versions of the plugins, please run Please note that the newer plugin versions are not compatible with Gauge 0.1.7. |
|
To solve the Context about this error: To know how many files are currently open, you can run the command |
|
While running Gauge 0.1.7 the below versions of plugins are used. While running Gauge 0.2.0 the below versions of plugins are used. 1)With Gauge 0.2.0, though I used the latest plugin versions. I typed in the command 'gauge --update-all'. It executed and ends with warning saying,
2)Now on running my specs for the first time it ran successfully and generated reports.Just with Plugin_kill_timeout incorrect value error. 3)From second time onwards it starts giving the same error message as mentioned in my previous post. [INFO] process /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/bin/java with pid 482 quit unexpectedly. exit status 1 Now I can see these warnings as well: On executing below command I get this value 1883 lsof | wc -l |
|
@vshanve Thanks for this info. Also, what number do you get when you run the command |
|
We have raised a separate issue for the incorrect timeout values. |
|
Unable to attach the logs for failure as txt file.So pasting it in my next post. I got 256 on running the below command ulimit -n Then I ran this command. *Now on running the specs its running successfully.Tried running different specs repeatedly. Its running good now.I dont see any error message now and the html reports got generated. *If I close my terminal and reopen a new one, I start seeing the issues again. Again if I pass those ulimit command I can run the specs successfully. *I can see this command is to set upper limit 'ulimit -S -n 2048' How it resolved everything? Thank you. |
|
09:17:23.334 [INFO] Note: Some input files use or override a deprecated API. |
|
Glad to know it is working fine now!
Thanks for the stacktrace. We have created a separate issue for that. I think reflections utility is not able to create new directories because of the upper limit set on number of files. But we need to confirm that. |
|
Thanks. I don't see this 'setting ulimit' issue if I run the specs using gauge 0.1.7. So is it an issue related only to 0.2.0 version? |
|
We have added a bunch of new features in 0.1.8 and in 0.2.0. We have also updated the dependencies in the new versions of Gauge. It's very likely that this may have increased the number of files that needs to be accessed. But we do not see it as a concern. Because to add more features, we have to add more files. Moreover, default upper limit of 256 is pretty low, especially in today's time. Most of the other unix based operating systems, including popular linux distros like ubuntu, fedora etc have 1024 as the default limit. I don't know why Apple has not increased it yet. |
|
Thank you again for your help. Was there a change between 0.1.7 and 0.1.8 effecting classpath or otherwise locating resources? From terminal the out folder was not generated, although gauge_bin was. I deleted both folders before running the tests. I'm wondering if gauge cannot find its own default values for the settings it's complaining about. xml-report is already installed. $gauge -v Pluginshtml-report (1.0.4) |
|
Perhaps I should open a new defect but after upgrading to 0.2.1 and running gauge --update-all I was able to run one spec successfully and pass but no reports were generated. After running a second time I got: 1: 12 "Incorrect value for runner_request_timeout in property file. Cannot convert to time" warnings Running gauge --version I get: Error starting plugin html-report. Failed to get plugin.json. Plugin html-report is not installed. To install, run Pluginsjava (0.3.1) And I now have four orphaned gauge processes on my Mac. This was following a reboot. |
|
After following the suggestion to increase the resources with "ulimit -S -n 2048" I was able to run a spec and generate a report. |
|
For the orphan processes, we have an open issue #166. We will be tracking it there. Glad to know that everything else has been resolved. We have added setting the I will take the liberty of closing this issue. Feel free to reopen in case you get this error again. |
Test were running with 0.1.7 on OS X but fail after upgrading to 0.1.8 with the following error. Looks like a conversion from null to a time value.
[WARNING] Incorrect value for runner_request_timeout in property file.Cannot convert to time
The text was updated successfully, but these errors were encountered: