[Octave-bug-tracker] [bug #53917] Incorrect warning: time stamp for 'filename' is in the future

[Ian McCallion]

Follow-up Comment #4, bug #53917 (project octave):

I have tried to do some more work on this, but when rerunning my original
scripts the error was not occurring. Even more peculiarly, I am now unable to
provoke the warning message even when the script file timestamp is a year in
the future as shown in this console log:


GNU Octave, version 4.4.0
Copyright (C) 2018 John W. Eaton and others.
This is free software; see the source code for copying conditions.
There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  For details, type 'warranty'.

Octave was configured for "x86_64-w64-mingw32".

Additional information about Octave is available at https://www.octave.org.

Please contribute if you find this software useful.
For more information, visit https://www.octave.org/get-involved.html

Read https://www.octave.org/bugs.html to learn how to submit bug reports.
For information about changes from previous versions, type 'news'.

>> system('touch dummy.m -t 201906011205') % make sure timestamp is well into
the future
ans = 0
>> system 'dir dummy.m'
 Volume in drive C is OS
 Volume Serial Number is 36F0-859C

 Directory of C:\Users\Ian

01/06/2019  12:05                 0 dummy.m
               1 File(s)              0 bytes
               0 Dir(s)  379,096,993,792 bytes free
ans = 0
>> warning on
>> dummy
>>

Hence I am at this point unable to do more experiments to further this bug
discussion.

I am unaware that I have made any changes to Octave between the time of my
original post and now. I get exactly the same behaviour on 4.2.2

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53917>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/