Generated 02.12.2022 09:25
Tested: FB40.   Build: 4.0.3.2880;   SS: 02.12.22 06:01:55 - 02.12.22 07:40:07;   CS: 02.12.22 07:42:30 - 02.12.22 09:23:28;
OS and hardware info:  Windows 10 10.0.19041 ; logical CPUs: 8 ; total memory: 31.7 Gb 

Test with at least one result = "FAIL" for last 30 runs:

NN	Test name	mode	4.0.3.2880 2022-12-02	4.0.3.2878 2022-11-27	4.0.3.2877 2022-11-25	4.0.3.2876 2022-11-25	4.0.3.2875 2022-11-16	4.0.3.2874 2022-11-12	4.0.3.2873 2022-11-05	4.0.3.2872 2022-11-04	4.0.3.2870 2022-11-03	4.0.3.2867 2022-11-01	4.0.3.2865 2022-10-29	4.0.3.2863 2022-10-27	4.0.3.2862 2022-10-25	4.0.3.2861 2022-10-20	4.0.3.2860 2022-10-17	4.0.3.2859 2022-10-15	4.0.3.2858 2022-10-12	4.0.3.2856 2022-10-10	4.0.3.2855 2022-10-05	4.0.3.2854 2022-10-02	4.0.3.2853 2022-10-01	4.0.3.2850 2022-09-27	4.0.3.2849 2022-09-24	4.0.3.2847 2022-09-21	4.0.3.2845 2022-09-18	4.0.3.2844 2022-09-15	4.0.3.2843 2022-09-14	4.0.3.2840 2022-09-13	4.0.3.2835 2022-09-09	4.0.3.2832 2022-09-07	Test TITLE
1	bugs core 4731 tracker	CS	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	F	F	F	F	F	P	P	P	P	P	P	P	P	P	Prohibit an ability to issue DML or DDL statements on RDB$ tables
2	bugs core 4731 tracker	SS	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	F	F	F	F	F	P	P	P	P	P	P	P	P	P	Prohibit an ability to issue DML or DDL statements on RDB$ tables
3	bugs core 5034 tracker	SS	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	F	P	P	P	At least 5 seconds delay on disconnect could happen if disconnect happens close after Event Manager initialization
4	bugs core 5435 tracker	CS	P	P	P	P	P	F	P	P	P	P	P	P	P	P	P	P	P	P	F	P	P	P	P	P	P	P	P	P	P	P	Badly selective index could be used for extra filtering even if selective index is used for sorting
5	bugs core 6095 tracker	SS	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	F	F	F	F	F	F	F	P	P	P	P	P	P	P	Extend trace record for COMMIT/ROLLBACK RETAINING to allow chaining of transaction ids
6	bugs gh 6875 tracker	CS	P	P	P	P	P	P	F	F	P	P	P	P	P	P	P	P	P	P	F	P	P	P	P	P	P	P	P	P	P	P	Significant performance regression of SIMILAR TO and SUBSTRING(SIMILAR) when pattern is taken from variable (rather than directly specified)
7	bugs gh 6875 tracker	SS	P	P	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Significant performance regression of SIMILAR TO and SUBSTRING(SIMILAR) when pattern is taken from variable (rather than directly specified)
8	replication blob not found in rw replica if target row exists	CS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Error "BLOB is not found" while replication converts INSERT into UPDATE for a conflicting record
9	replication blob not found in rw replica if target row exists	SS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Error "BLOB is not found" while replication converts INSERT into UPDATE for a conflicting record
10	replication blob segments longer 32kb are not replicated	CS	F	F	P	P	F	F	P	P	P	P	P	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Problem with replication of BLOB segments longer than 32KB
11	replication blob segments longer 32kb are not replicated	SS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Problem with replication of BLOB segments longer than 32KB
12	replication dblevel triggers must not fire on replica	CS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Replica DB must not fire DB-level triggers but their activity on master must be eventually seen in replica.
13	replication dblevel triggers must not fire on replica	SS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Replica DB must not fire DB-level triggers but their activity on master must be eventually seen in replica.
14	replication ddl triggers must not fire on replica	CS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	DDL-triggers must fire only on master DB.
15	replication ddl triggers must not fire on replica	SS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	DDL-triggers must fire only on master DB.
16	replication duplicates in rw replica after conflicting insert	CS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Conflicting INSERT propagated into a read-write replica may cause duplicate records to appear
17	replication duplicates in rw replica after conflicting insert	SS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Conflicting INSERT propagated into a read-write replica may cause duplicate records to appear
18	replication failed ddl commands can be replicated	CS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Failed DDL commands can be replicated
19	replication failed ddl commands can be replicated	SS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Failed DDL commands can be replicated
20	replication generator could not be transferred to replica	CS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Generator values may not replicate after commit
21	replication generator could not be transferred to replica	SS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Generator values may not replicate after commit
22	replication invalid msg if target db has no replica flag	CS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set
23	replication invalid msg if target db has no replica flag	SS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set
24	replication permission error on ddl issued by non sysdba	CS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Permission error with replication
25	replication permission error on ddl issued by non sysdba	SS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Permission error with replication
26	replication shutdown during applying segments leads to crash	CS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Crash or hang while shutting down the replica database if segments are being applied
27	replication shutdown during applying segments leads to crash	SS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Crash or hang while shutting down the replica database if segments are being applied
28	replication some updates crash server on replica side	CS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Some updates can crash Firebird server on replica side
29	replication some updates crash server on replica side	SS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Some updates can crash Firebird server on replica side
30	replication updating blob with empty string stops replication	CS	F	F	P	P	F	F	P	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Replication gets stuck due to "Blob xxx.xx is not found for table xxx" error
31	replication updating blob with empty string stops replication	SS	F	F	P	P	F	F	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	P	Replication gets stuck due to "Blob xxx.xx is not found for table xxx" error

Elapsed time, milliseconds:

NN	Test name	mode	median_ms	4.0.3.2880 2022-12-02	4.0.3.2878 2022-11-27	4.0.3.2877 2022-11-25	4.0.3.2876 2022-11-25	4.0.3.2875 2022-11-16	4.0.3.2874 2022-11-12	4.0.3.2873 2022-11-05	4.0.3.2872 2022-11-04	4.0.3.2870 2022-11-03	4.0.3.2867 2022-11-01	4.0.3.2865 2022-10-29	4.0.3.2863 2022-10-27	4.0.3.2862 2022-10-25	4.0.3.2861 2022-10-20	4.0.3.2860 2022-10-17	4.0.3.2859 2022-10-15	4.0.3.2858 2022-10-12	4.0.3.2856 2022-10-10	4.0.3.2855 2022-10-05	4.0.3.2854 2022-10-02	4.0.3.2853 2022-10-01	4.0.3.2850 2022-09-27	4.0.3.2849 2022-09-24	4.0.3.2847 2022-09-21	4.0.3.2845 2022-09-18	4.0.3.2844 2022-09-15	4.0.3.2843 2022-09-14	4.0.3.2840 2022-09-13	4.0.3.2835 2022-09-09	4.0.3.2832 2022-09-07	Test TITLE
1	bugs core 4731 tracker	CS	8775	9050	8780	8900	8850	8880	8650	8940	8780	8770	8710	8820	8720	8820	9780	8660	8640	8590	8860	8630	8880	9180	8730	8690	8660	8790	8640	8910	8670	8340	8350	Prohibit an ability to issue DML or DDL statements on RDB$ tables
2	bugs core 4731 tracker	SS	5510	5470	5470	5420	5350	5430	5970	5490	5530	5460	6110	6460	5680	5580	5590	5570	5450	5360	5640	5780	5450	5470	5450	5440	5960	5640	5470	5890	6110	5550	5190	Prohibit an ability to issue DML or DDL statements on RDB$ tables
3	bugs core 5034 tracker	SS	16180	13940	16190	17490	16190	14460	16380	16110	16080	17040	15910	15960	17440	16530	17530	15810	16840	17180	17820	17210	17330	14200	15710	14810	15450	16140	16730	15720	14800	16170	16800	At least 5 seconds delay on disconnect could happen if disconnect happens close after Event Manager initialization
4	bugs core 5435 tracker	CS	5620	5610	5680	5650	5480	5720	5660	5610	5770	5610	5770	5660	5720	5730	6030	5610	5560	6040	5580	5580	5560	5630	5590	5610	5670	5800	5580	5600	5610	5800	5240	Badly selective index could be used for extra filtering even if selective index is used for sorting
5	bugs core 6095 tracker	SS	5090	5060	5080	5060	4980	5090	5080	5060	5080	5070	5110	5120	5650	5120	5620	5050	5140	5030	5110	5570	5140	5090	5120	5090	5090	5580	5570	5660	5090	4890	4890	Extend trace record for COMMIT/ROLLBACK RETAINING to allow chaining of transaction ids
6	bugs gh 6875 tracker	CS	3110	3150	3150	3080	3560	3580	3150	3740	3660	3090	3000	3160	3230	3910	3080	3460	3350	3050	3110	3830	3110	3080	3060	3060	3100	3000	3020	3040	3190	3000	2970	Significant performance regression of SIMILAR TO and SUBSTRING(SIMILAR) when pattern is taken from variable (rather than directly specified)
7	bugs gh 6875 tracker	SS	3030	3140	3360	3570	2960	3020	3100	3050	3080	3030	3030	4690	3050	3040	3000	3010	3100	2970	3060	3000	3040	3030	3000	2990	3270	3050	3030	3010	3030	3020	3000	Significant performance regression of SIMILAR TO and SUBSTRING(SIMILAR) when pattern is taken from variable (rather than directly specified)
8	replication blob not found in rw replica if target row exists	CS	11220	201070	200410	9720	11390	200470	200820	9760	10760	11950	12130	10940	11860	11050	11450	11890	11960	8610	10990	10360	10180	10900	10970	10070	11680	12200	10600	11710	12060	9270	10350	Error "BLOB is not found" while replication converts INSERT into UPDATE for a conflicting record
9	replication blob not found in rw replica if target row exists	SS	11255	200110	200590	11360	11050	200180	200200	11690	9380	10550	11760	9700	12760	11680	10550	11550	8940	10400	12460	12410	12520	9370	10530	10540	9530	10530	11150	12610	10650	11440	9790	Error "BLOB is not found" while replication converts INSERT into UPDATE for a conflicting record
10	replication blob segments longer 32kb are not replicated	CS	6080	134060	134890	5830	5670	134220	134000	5860	5980	6020	9030	6040	71970	6060	6080	5850	5840	6880	5910	5960	5940	6200	5870	8410	6080	7780	6090	6740	5580	6230	6360	Problem with replication of BLOB segments longer than 32KB
11	replication blob segments longer 32kb are not replicated	SS	6615	134050	133590	6550	6440	133730	133800	6730	6570	6630	5620	6630	5640	6680	6640	6640	6620	6430	6610	5530	5620	6560	6630	6610	6670	6580	6630	5600	5550	6110	7090	Problem with replication of BLOB segments longer than 32KB
12	replication dblevel triggers must not fire on replica	CS	6075	134010	134300	5840	5720	134290	134090	5870	6010	6040	9020	7090	6210	6220	6070	5960	5900	5860	5910	6060	5990	8450	5940	6300	6080	8070	7020	5920	6180	6360	5510	Replica DB must not fire DB-level triggers but their activity on master must be eventually seen in replica.
13	replication dblevel triggers must not fire on replica	SS	5725	133580	133590	6610	5480	133850	133580	5630	5590	5640	6760	5650	6710	5680	5710	5700	5630	6460	5580	6560	6640	5570	5680	5670	5570	5620	6000	6680	7950	5740	6160	Replica DB must not fire DB-level triggers but their activity on master must be eventually seen in replica.
14	replication ddl triggers must not fire on replica	CS	7035	154940	155270	7700	6600	155310	155190	6740	6880	6890	6860	6980	7130	6900	6960	6830	7800	6640	6830	7360	6880	7040	6800	7040	7180	7030	6920	9000	7310	7100	8300	DDL-triggers must fire only on master DB.
15	replication ddl triggers must not fire on replica	SS	7490	154590	155100	7410	7240	154000	154630	7400	7390	7430	7490	8620	7450	7490	7450	8400	7780	6220	7410	7410	7410	7370	7440	7440	8420	8840	10570	7510	10460	9040	7920	DDL-triggers must fire only on master DB.
16	replication duplicates in rw replica after conflicting insert	CS	9900	200360	200710	8800	10450	200730	200630	9000	9860	9900	8850	9070	9030	9920	10000	9830	9790	9420	9710	9820	9900	9900	9000	9060	9920	10010	9870	11130	10010	10610	10140	Conflicting INSERT propagated into a read-write replica may cause duplicate records to appear
17	replication duplicates in rw replica after conflicting insert	SS	10000	200180	199990	9310	10200	200160	200580	10360	9390	10000	9450	9620	9530	10000	9470	8980	10470	10140	10330	9400	9520	9450	10000	10520	9390	9490	9520	10550	10410	10890	9840	Conflicting INSERT propagated into a read-write replica may cause duplicate records to appear
18	replication failed ddl commands can be replicated	CS	6285	134400	134360	6090	5970	134410	134550	6120	5720	6380	6330	6780	6240	6350	6350	6200	9140	5830	6230	6230	6230	6340	6160	6360	6360	6370	6240	8560	6230	5000	5920	Failed DDL commands can be replicated
19	replication failed ddl commands can be replicated	SS	6485	134460	133980	6770	5660	133990	133820	5000	6760	5850	6940	5950	7470	5890	5910	6260	5850	6630	6800	6800	5850	6850	5890	5950	6810	5840	7100	5920	5990	6340	7320	Failed DDL commands can be replicated
20	replication generator could not be transferred to replica	CS	6420	134490	135060	6180	6080	134480	134660	6230	6390	6360	6410	9720	6980	8470	8520	6370	8400	6080	6350	6310	5920	6400	6340	6430	8440	6560	6440	6000	6360	6520	6680	Generator values may not replicate after commit
21	replication generator could not be transferred to replica	SS	6705	133930	134110	5900	6760	134140	133950	6930	5950	6990	6200	6080	8020	7060	6060	6420	6020	5780	5920	5920	7000	5970	5990	7000	5920	6960	6650	7010	6940	7470	6400	Generator values may not replicate after commit
22	replication invalid msg if target db has no replica flag	CS	10580	134080	134400	10950	9760	134290	134170	11110	10130	10090	10100	13280	12280	11110	10200	13170	10980	10820	10070	10010	10170	10180	10120	10300	11150	10000	10210	11060	10040	10340	11440	Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set
23	replication invalid msg if target db has no replica flag	SS	10790	133620	133610	10710	10610	133740	133720	10780	10760	9780	9960	10840	10890	9840	10810	10790	10860	10650	10720	10730	10830	10790	10870	10860	10710	10810	12840	10880	10790	10300	10490	Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set
24	replication permission error on ddl issued by non sysdba	CS	3685	133660	133800	5540	3350	133860	133830	5580	3670	3540	3700	5690	3550	5720	3610	5700	5570	3390	3540	3580	3730	3560	3630	3650	5570	3800	3560	5600	3530	2900	2960	Permission error with replication
25	replication permission error on ddl issued by non sysdba	SS	15020	132810	132880	14920	14860	132950	132930	13980	14990	15020	15040	15040	15080	15030	15000	15010	14970	14830	15140	15000	14030	14960	15080	15020	15010	15040	15000	15090	15040	16080	14580	Permission error with replication
26	replication shutdown during applying segments leads to crash	CS	17330	411880	412560	25470	7610	412340	412320	17370	17260	18130	17770	17340	17330	17000	17350	17310	7770	16820	17290	17240	17460	17350	17330	10260	17260	10100	17440	17320	18270	14280	14310	Crash or hang while shutting down the replica database if segments are being applied
27	replication shutdown during applying segments leads to crash	SS	38405	410550	411240	39070	45690	411000	410980	39140	35110	39160	39370	38610	35060	36050	35510	35230	35310	36110	35180	39170	36070	36390	36200	35070	39660	35830	39280	46360	38200	34380	49290	Crash or hang while shutting down the replica database if segments are being applied
28	replication some updates crash server on replica side	CS	6545	134060	133970	5930	5640	134000	133960	6000	6800	8780	8870	5770	5830	8890	5800	6830	8680	7000	5000	5790	6760	5770	6300	7830	6780	6000	6330	5730	8730	6120	6220	Some updates can crash Firebird server on replica side
29	replication some updates crash server on replica side	SS	27150	132720	132730	27000	30440	133010	132800	27150	30210	27140	27130	27320	30210	27150	27140	28080	30140	26970	27050	30140	27100	27110	27070	27070	26130	27200	27070	30440	27080	30730	27000	Some updates can crash Firebird server on replica side
30	replication updating blob with empty string stops replication	CS	6115	134070	134220	6120	5620	134290	134330	9050	72010	6030	6030	6050	6050	6070	5990	6080	5890	7700	6040	6120	9090	6110	6060	7040	6060	11000	6130	6070	5840	6270	6380	Replication gets stuck due to "Blob xxx.xx is not found for table xxx" error
31	replication updating blob with empty string stops replication	SS	27595	133480	133260	27260	30560	133310	133220	27350	30410	30410	27330	27350	27350	27360	27320	27260	30370	27080	30420	30390	27320	27310	27310	30360	27330	31760	30430	27580	31350	24770	27610	Replication gets stuck due to "Blob xxx.xx is not found for table xxx" error

List of tests in this report: