Details
Description
https://buildbot.mariadb.org/#/builders/50/builds/11/steps/5/logs/stdio
it shoud uses size_t instead of long for sizes. Also more tests are welcome.
disks.disks w14 [ fail ]
|
Test ended at 2020-05-29 11:34:19
|
CURRENT_TEST: disks.disks
|
--- /buildbot/32bit-ubuntu-1804/build/plugin/disks/mysql-test/disks/disks.result 2020-05-29 11:23:53.000000000 +0000
|
+++ /buildbot/32bit-ubuntu-1804/build/plugin/disks/mysql-test/disks/disks.reject 2020-05-29 11:34:19.644705159 +0000
|
@@ -9,4 +9,4 @@
|
) ENGINE=MEMORY DEFAULT CHARSET=utf8
|
select sum(Total) > sum(Available), sum(Total)>sum(Used) from information_schema.disks;
|
sum(Total) > sum(Available) sum(Total)>sum(Used)
|
-1 1
|
+0 1
|
mysqltest: Result content mismatch
|
it should actually use ulonglong, not size_t and especially not long . Never use long, it serves no purpose.
The reason for ulonglong is that disks are bigger than 4GB, even on on 32bit. Even if you count KB, there are now disks that are 4TB big