Misleading time marks in WU and tasks status

Forums › Problems and Bug Reports

Mad_Max
Mad_Max
Joined: 2 Jan 10
Posts: 165
Credit: 2261312209
RAC: 662626
31 Mar 2019 22:02:09 UTC
Topic 218550
(moderation:
    )

    Hello.

    During hunting down previous error I have noticed that E@H BOINC server shows time marks in task status in a misleading way.

    Its state time in "GMT" time zone, but actually it DOES time zone corrections to user local time zone and so it is NOT a GMT. But only if user is already logged in.
    For example (it happens with all task so literally any task will do) this task: https://einsteinathome.org/task/841811803

    If i open this link without log in to my account i see this:

     Name: LATeah1059L_188.0_0_0.0_47444159_1
 Workunit ID: 398540651
 Created: 31 Mar 2019 20:22:41 GMT
 Sent: 31 Mar 2019 20:31:32 GMT
 Report deadline: 14 Apr 2019 20:31:32 GMT

    After login to my account i see this on the same task status:

    Name: LATeah1059L_188.0_0_0.0_47444159_1
Workunit ID: 398540651
Created: 31 Mar 2019 23:22:41 GMT
Sent: 31 Mar 2019 23:31:32 GMT
Report deadline: 14 Apr 2019 23:31:32 GMT

    After logon server added +3 hours to my local time zone (GMT+3 - from the account settings) - its OK by itself. But server still writes "GMT" while it is no longer a GMT time. It turns out the actual error - 23 GMT is a wrong time here. Correct time for this example task is 20 GMT OR 23 MSK (GMT+3), but not 23 GMT.

    In overall tasks list (https://einsteinathome.org/account/tasks/active) server always shows time in UTC regardless of user timezone setting in account. And its OK too. But in the status/details per individual task - it represent time marks really weird and misleading.

    For other example WU (not task) status: https://einsteinathome.org/workunit/398540651

    After login in i see:

     Workunit 398540651
 Name: LATeah1059L_188.0_0_0.0_47444159
 Application: Gamma-ray pulsar binary search #1 on GPUs
 Created: 31 Mar 2019 23:22:39 GMT

    Task ID

      Computer Sent Time reported or deadline Status Run time CPU time Granted credit Application
    LATeah1059L_188.0_0_0.0_47444159_0
    		 12670483 31 Mar 2019 20:30:40 UTC 14 Apr 2019 20:30:40 UTC In progress 0.00 0.00 0 Gamma-ray pulsar binary search #1 on GPUs v1.18 (FGRPopencl1K-ati) windows_x86_64
    LATeah1059L_188.0_0_0.0_47444159_1
    		 12204611 31 Mar 2019 20:31:32 UTC 14 Apr 2019 20:31:32 UTC In progress 0.00 0.00 0 Gamma-ray pulsar binary search #1 on GPUs v1.18 (FGRPopencl1K-ati) windows_x86_64

    It is looks like tasks were sent even BEFORE corresponding WU was created. But of course this is not the case - just the WU creation time shown is incorrect. Its actually a 31 Mar 2019 20:22:39 GMT/UTC and first task was sent 8 mins later at 31 Mar 2019 20:30:40 GMT/UTC

    Shawn Kwang
    Shawn Kwang
    Joined: 3 Nov 15
    Posts: 289
    Credit: 3201752
    RAC: 2031

    Thanks for bringing this to

    1 Apr 2019 12:17:54 UTC
    Message 170437
    (moderation:
      )

      Thanks for bringing this to our attention. I will have to look into it with more detail. But it's on my radar at least.

      Einstein@Home Project

      Shawn Kwang
      Shawn Kwang
      Joined: 3 Nov 15
      Posts: 289
      Credit: 3201752
      RAC: 2031

      This timezone display problem

      11 Apr 2019 13:29:51 UTC
      Message 170649
      (moderation:
        )

        This timezone display problem should be fixed. All times have been converted to be shown in UTC.

        Einstein@Home Project

        Mad_Max
        Mad_Max
        Joined: 2 Jan 10
        Posts: 165
        Credit: 2261312209
        RAC: 662626

        Yes, all looks fine now: all

        14 Apr 2019 22:21:09 UTC
        Message 170707
        (moderation:
          )

          Yes, all looks fine now: all time stamps in UTC everywhere.

          Thank you

          Mad_Max
          Mad_Max
          Joined: 2 Jan 10
          Posts: 165
          Credit: 2261312209
          RAC: 662626

          Looks like fix of timezone

          22 Apr 2019 0:08:08 UTC
          Message 170864
          (moderation:
            )

            Looks like fix of timezone caused another minor glitch - now unsent tasks in WU displays as sent at 1 Jan 1970 0:00:00 UTC

            Probable it is a unix time conversion of zero value or of uninitialized variable.

            Example of WU - https://einsteinathome.org/workunit/400859556

            Shawn Kwang
            Shawn Kwang
            Joined: 3 Nov 15
            Posts: 289
            Credit: 3201752
            RAC: 2031

            Thanks. It's because the

            29 Apr 2019 20:21:20 UTC
            Message 171053 in response to message 170864
            (moderation:
              )

              Thanks. It's because the initial time in the database is indeed 0, or Jan 1 1970. I'll look into fixing this.

              Einstein@Home Project

              Richard Haselgrove
              Richard Haselgrove
              Joined: 10 Dec 05
              Posts: 2143
              Credit: 3024802934
              RAC: 1485926

              See the default php include

              29 Apr 2019 21:51:12 UTC
              Message 171054 in response to message 171053
              (moderation:
                )

                See the default php include file for the equivalent BOINC display: https://github.com/BOINC/boinc/blob/master/html/inc/result.inc#L459

                Null or zero values are explicitly set like

                $cpu_time = "---";
$elapsed_time = "---";

                Comment viewing options

                Select your preferred way to display the comments and click "Save settings" to activate your changes.

                Forums › Problems and Bug Reports