-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New_York time-zone not supported in default capabilities for Selenium/Saucelabs? #1287
Comments
This seems to occur for any timezone with an underscore in the name, e.g. Workaround: |
Actually, Eastern gets accepted but doesn't seem to change the time zone to EST. Looks like the VM remains in the default UTC. I've tried Detroit (works), Chicago (works with expected time difference failures), and London (works w/ expected time diffs). So right now my workaround is Detroit... |
Workaround #2 - use |
I'm closing this since the issue has been brought up with sauce labs and isn't specific to protractor at all. |
Hi! Could you help me. How to set local/custom time zone for protractor test? |
You are reacting on a closed issue. I don't think this is smart. Secondly your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help. From the the getting help section of the README:
Thanks! |
I don't know if this is an issue on the protractor side or the SauceLabs side, but I'm trying to change the time zone of a SauceLabs VM using defaultCapabilities in the protractor config file to EST (New_York):
exports.config.multiCapabilities = [_.assign({}, defaultCapabilities, {
"time-zone": "New_York",
"browserName": "firefox",
"version": "30"
}), _.assign({}, defaultCapabilities, {
"time-zone": "New_York",
"browserName": "chrome",
"version": "35",
"platform": "OS X 10.9"
})];
I receive an error that it is an unsupported time zone. When I pass in Chicago or Detroit, it works as expected. When I pass in New_York, it says it is unsupported. Thoughts?
The text was updated successfully, but these errors were encountered: