Comment 7 for bug 1328600

Still investigating this to see where the easiest fix lies, along with the real source of the issues. Looking at the toolkit, you could adjust the maximum property for the datepicker objects to avoid this issue. Adjusting the qml for the affected tests to set a lower maximum property does work, and the display is updated to reflect the new max year properly.

However, the default maxyear (currently 2064) object still exists. It's seemingly being created by AP? It's unclear.