versioning.partition 'innodb,timestamp'  w3 [ fail ]

        Test ended at 2018-04-05 13:01:06

CURRENT_TEST: versioning.partition

--- D:/win32-debug/build/src/mysql-test/suite/versioning/r/partition.result	2018-04-05 12:41:27.156723600 +0000

+++ D:\win32-debug\build\src\mysql-test\suite\versioning\r\partition.reject	2018-04-05 13:01:06.431516900 +0000

@@ -495,7 +495,11 @@

 subpartition by key (i) subpartitions 2

 (partition p1 history, partition pn current);

 insert t1 values (1);

+Warnings:

+Warning	4114	Versioned table `test`.`t1`: partition `p1` is full, add more HISTORY partitions

 delete from t1;

+Warnings:

+Warning	4114	Versioned table `test`.`t1`: partition `p1` is full, add more HISTORY partitions

 insert t1 values (2);

 Warnings:

 Warning	4114	Versioned table `test`.`t1`: partition `p1` is full, add more HISTORY partitions

@@ -505,12 +509,12 @@

 alter table t1 add partition (partition p0 history, partition p2 history);

 select subpartition_name,table_rows from information_schema.partitions where table_schema='test' and table_name='t1';

 subpartition_name	table_rows

-p1sp0	1

+p1sp0	0

 p1sp1	0

-p0sp0	0

-p0sp1	1

+p0sp0	1

+p0sp1	0

 p2sp0	0

-p2sp1	0

+p2sp1	1

 pnsp0	0

 pnsp1	0

 ## pruning check

@@ -533,7 +537,7 @@

 1

 explain partitions select * from t1 for system_time all where row_end = @ts;

 id	select_type	table	partitions	type	possible_keys	key	key_len	ref	rows	Extra

-1	SIMPLE	t1	p1_p1sp0,p1_p1sp1	#	NULL	NULL	NULL	NULL	#	#

+1	SIMPLE	t1	p0_p0sp0,p0_p0sp1	#	NULL	NULL	NULL	NULL	#	#

 #

 # MDEV-15103 Assertion in ha_partition::part_records() for updating VIEW

 #

can be observed in https://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/8160/steps/test/logs/stdio for example.

It also fails if precise version of Windows timer is used.