The tstamp (antunit) test named "testMagicProperty" has been consistently failing (only) on Windows for a while now[1]. Both master and 1.9.x branches. The failure looks really odd and something that I haven't been able to understand yet. The one interesting bit to this failure, based on what I can find in the history, is that it fails only on "windows-2016" node(s) but has passed (and still passes) on "windows-2012" node(s).
Looking at the tstamp task code, I haven't yet found out what can lead to this issue. The only way I can think of this happening is that the number of seconds being added to the epoch is less than a day's value - which isn't the case in that test case which adds 100000 seconds. https://builds.apache.org/job/Ant-Build-Matrix-master-Windows/jdk=JDK%201.8.0_121%20(unlimited%20security)%2064-bit%20Windows%20only,label_exp=Windows/lastCompletedBuild/testReport/src.tests.antunit.taskdefs/tstamp-test_xml/testMagicProperty/ -Jaikiran --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
