Bug#863934: fix
On 2017, ജൂൺ 20 12:11:57 PM IST, "Jérémy Lal"wrote: >I'm pretty sure it does. > >Jérémy TZ=GMT did not work, but TZ=UTC worked.
Bug#863934: fix
2017-06-20 7:31 GMT+02:00 Pirate Praveen: > On Mon, 19 Jun 2017 07:57:23 +0200 Paolo Greppi > wrote: > > According to upstream (https://github.com/felixge/ > node-dateformat/issues/21) "dateformat() doesn't really play well with > timezones since the javascript Date() object itself doesn't really play > well with timezones." > > > > We should be content with fixing the tests for the GMT timezone using > the trick suggested by kapouer (https://github.com/felixge/ > node-dateformat/issues/41#issuecomment-286419133): > > > > TZ=GMT mocha -R spec > > > > Paolo > > > > > > Paolo, > > In rules, its already > TZ=Etc/UTC mocha -R spec > > Do you think TZ=GMT will fix it? > > I'm pretty sure it does. Jérémy
Bug#863934: fix
On Mon, 19 Jun 2017 07:57:23 +0200 Paolo Greppiwrote: > According to upstream (https://github.com/felixge/node-dateformat/issues/21) > "dateformat() doesn't really play well with timezones since the javascript > Date() object itself doesn't really play well with timezones." > > We should be content with fixing the tests for the GMT timezone using the > trick suggested by kapouer > (https://github.com/felixge/node-dateformat/issues/41#issuecomment-286419133): > > TZ=GMT mocha -R spec > > Paolo > > Paolo, In rules, its already TZ=Etc/UTC mocha -R spec Do you think TZ=GMT will fix it? signature.asc Description: OpenPGP digital signature
Bug#863934: fix
According to upstream (https://github.com/felixge/node-dateformat/issues/21) "dateformat() doesn't really play well with timezones since the javascript Date() object itself doesn't really play well with timezones." We should be content with fixing the tests for the GMT timezone using the trick suggested by kapouer (https://github.com/felixge/node-dateformat/issues/41#issuecomment-286419133): TZ=GMT mocha -R spec Paolo