It appears there is a bug with the America/Sao_Paulo time zone; specifically, with the 2014-02-15/16 DST change. Not sure the best way to confirm and/or if there is someone that can quickly check/verify. Thoughts?

I found this while working with java and noticed it after upgrading from adoptopenjdk version 8u222_b10 to version 8u232_b09. I believe 222 utilizes tzdata2019a while 232 utilizes tzdata2019c. I understand that there are many things that could cause the issue from the code running in java down the stack to the tzdata; however, believe tzdata is the most likely culprit.

Any thoughts/ideas of how to track this down?

Thank you,

Bryan

Reference Output:

jdk 8.222_b10
2014-02-15 23:59:59 BRST: 1392515999000
2014-02-15 23:00:00 BRST: 1392512400000
2014-02-15 23:00:00 BRT : 1392516000000
2014-02-16 00:00:00 BRST: 1392516000000
2014-02-16 00:00:00 BRT : 1392519600000

jdk 8.232_b09
2014-02-15 23:59:59 BRST: 1392519599000
2014-02-15 23:00:00 BRST: 1392516000000
2014-02-15 23:00:00 BRT : 1392516000000
2014-02-16 00:00:00 BRST: 1392519600000
2014-02-16 00:00:00 BRT : 1392519600000