You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2021/11/30 13:22:00 UTC

[jira] [Commented] (DAFFODIL-1505) time zone behavior depends on machine where daffodil is running

    [ https://issues.apache.org/jira/browse/DAFFODIL-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451119#comment-17451119 ] 

Dave Thompson commented on DAFFODIL-1505:
-----------------------------------------

Test test_timeZoneFormats7 still does not round trip on v3.2.0 pre-release. Test still does not unparse to the expected value of "08:43.Eastern Standard Time" (original source) as identified in 27/Jan/2021 comment.

> time zone behavior depends on machine where daffodil is running
> ---------------------------------------------------------------
>
>                 Key: DAFFODIL-1505
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1505
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End, General
>    Affects Versions: 2.0.0
>            Reporter: Mike Beckerle
>            Priority: Minor
>
> test test_timeZoneFormats7 fails running "round trip" on the bamboo automatic build server.
> However it passes on all developers workstations.
> The suggested cause is that Daffodil unparsing is using the ICU libraries, and we're not controlling all the parameters of time-zone behavior, and that is leaving some unparser behavior to be inherited from the installation. 
> Since the NCSA bamboo server is in Central Time Zone (US), that's different from the Tresys developers all of whom are Eastern Time Zone (US). 
> This is a bug, because DFDL processors are not supposed to have any behavior that depends on the installation locale, but rather all behavior depends on the DFDL schema and external variables that schema provides. 
> The installation locale for the DFDL processor can affect error-message language/locale, but not what happens in parsing or unparsing of data. 
> So we need to track down what is not being adequately specified here, and control that.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)