Timezone Bug

[wcandillon]

cc @paul-j-lucas

The following query:

xs:time("00:00:00+01:00") lt xs:time("00:00:00+02:00")
,
xs:time("00:00:00+01:00") lt xs:time("00:00:00+00:00")

Returns:
true true (see http://try.zorba.io/queries/xquery/NyRQ%2BE8HJajJoAhXjwuFLt3Q8K8%3D)
Other xquery processors (basex, exist-db) return false true. We believe that fixing this bug will solve will solve the remaining failing FOTS tests (these were not run on Zorba Jenkins).

[wcandillon]

A good test for the resolution of this bug is to make a PR against https://github.com/28msec/zorba/tree/w3c_tests it should fix the build status on this branch.

[MatthiasBrantner]

What’s the name of the test? I would like to check if I find something about it in my
email archive.

Thanks

Matthias

On May 27, 2014, at 4:28 AM, William Candillon [email protected] wrote:

cc @paul-j-lucas

The following query:

xs:time("00:00:00+01:00") lt xs:time("00:00:00+02:00")
,
xs:time("00:00:00+01:00") lt xs:time("00:00:00+00:00")
Returns:
true true (see http://try.zorba.io/queries/xquery/NyRQ%2BE8HJajJoAhXjwuFLt3Q8K8%3D)
Other xquery processors (basex, exist-db) return false true. We believe that fixing this bug will solve will solve the remaining failing FOTS tests (these were not run on Zorba Jenkins).

—
Reply to this email directly or view it on GitHub.

[wcandillon]

According to which timezone is configured, it can be:
FOTS/prod-WhereClause (Failed)
Or
FOTS/op-time-greater-than (Failed)
FOTS/op-time-less-than (Failed)

Please note that I am not 100% positive that the fix for this bug will fix the zorba build. It's just a strong suspicion.

[wcandillon]

@paul-j-lucas Would it be possible to raise priority on this bug (if possible)? I'm a bit worried because this bug prevents to use the full blown patch-queue for all the other fixes which are currently being submitted.

[paul-j-lucas]

It's possible, but you'd have to ask Matthias.

• Paul

On Jun 11, 2014, at 9:13 AM, William Candillon [email protected] wrote:

@paul-j-lucas Would it be possible to raise priority on this bug (if possible)? I'm a bit worried because this bug prevents to use the full blown patch-queue for all the other fixes which are currently being submitted.

—
Reply to this email directly or view it on GitHub.