1
0
mirror of https://github.com/MariaDB/server.git synced 2025-07-27 18:02:13 +03:00

events in perfschema tests: use ON COMPLETION NOT PRESERVE

when the execution is very slow, under valgrind,
the event might manage to fire more than once, making the
test to fail
This commit is contained in:
Sergei Golubchik
2024-03-27 09:51:28 +01:00
parent 49f2e9f700
commit dc681953cf
3 changed files with 6 additions and 6 deletions

View File

@ -145,7 +145,7 @@ Bollywood
# Event
SET GLOBAL event_scheduler=ON;
CREATE TABLE table_t(a INT);
CREATE EVENT e1 ON SCHEDULE EVERY 2 SECOND DO
CREATE EVENT e1 ON SCHEDULE EVERY 2 SECOND ON COMPLETION NOT PRESERVE DO
BEGIN
INSERT INTO table_t VALUES(1);
END|
@ -165,7 +165,7 @@ statement/sql/call_procedure CALL SampleProc1(30,40,50) NULL NULL 0
statement/sql/call_procedure CALL SampleProc2("Jwalamukhi",34) NULL NULL 0
statement/sql/call_procedure CALL SampleProc3() NULL NULL 0
statement/sql/call_procedure CALL SampleProc4() NULL NULL 0
statement/sql/create_event CREATE EVENT e1 ON SCHEDULE EVERY 2 SECOND DO
statement/sql/create_event CREATE EVENT e1 ON SCHEDULE EVERY 2 SECOND ON COMPLETION NOT PRESERVE DO
BEGIN
INSERT INTO table_t VALUES(1);
END NULL NULL 0