01. Total results for each kind of outcome and server mode, for previous 30 runs
02. NEW CRASHES/BUGCHECKS: tests that caused FB abnormal termination for LAST run (0 rows)
03. NEW FAILS: tests which failed for LAST run (0 rows)
04. NEW ERRORS: tests which raised runtime error for LAST run (0 rows)
05. STILL FAILS: tests which fail for at least TWO LAST runs (0 rows)
[CURRENT] 06. Has fails: tests with at least one fail for previous 30 runs (15 rows)
07. Has runtime errors: tests with at least one runtime error for previous 30 runs (0 rows)
08. Has crashes/bugchecks: tests that caused FB abnormal termination for previous 30 runs (0 rows)
09. NEW PASSED: successful tests for last run and outcome = FAIL/ERROR/SKIPPED or absent previously (9 rows)
10. All tests: outcomes for previous 30 runs (2406 rows)
11. All tests: durations for previous 30 runs (4664 rows)
12. Skipped: tests which was intentionally excluded from execution (66 rows)

Generated 17.05.2024 08:22
Tested: FB40.   Build: 4.0.5.3100;   SS: 17.05.24 06:41:56 - 17.05.24 07:25:50;   CS: 17.05.24 07:26:34 - 17.05.24 08:21:37;
OS and hardware info:  Windows 10 10.0.19045 ; logical CPUs: 8 ; total memory: 31.7 Gb 
QA-software: Python 3.11.2; pytest: 7.4.4; firebird.driver: 1.10.4; Firebird.Qa: 0.19.3

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

Jump to LIST of unique test names from this report

NN Test name mode 4.0.5.3100
2024-05-17
4.0.5.3098
2024-05-15
4.0.5.3092
2024-05-08
4.0.5.3091
2024-04-30
4.0.5.3089
2024-04-27
4.0.5.3088
2024-04-19
4.0.5.3086
2024-04-17
4.0.5.3083
2024-04-13
4.0.5.3082
2024-03-26
4.0.5.3081
2024-03-23
4.0.5.3080
2024-03-19
4.0.5.3078
2024-03-16
4.0.5.3077
2024-03-15
4.0.5.3066
2024-03-13
4.0.5.3065
2024-03-12
4.0.5.3064
2024-03-10
4.0.5.3062
2024-03-01
4.0.5.3061
2024-02-21
4.0.5.3059
2024-02-18
4.0.5.3058
2024-02-13
4.0.5.3057
2024-02-12
4.0.5.3056
2024-02-11
4.0.5.3055
2024-02-10
4.0.5.3054
2024-02-04
4.0.5.3053
2024-01-30
4.0.5.3052
2024-01-26
4.0.5.3051
2024-01-25
4.0.5.3050
2024-01-15
4.0.5.3049
2023-12-30
4.0.5.3045
2023-12-21
Test TITLE
1 CS 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 P
Count ( DISTINCT ... ) is too slow
2 CS P F P P P P P P P P P P F P P P P P F P P P P P P P P P P P
Compress Data over the Network
3 SS P F P P P P P P P P P P P P P P P P P P P P F P P P P P P P
Compress Data over the Network
4 SS 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 P
Ability to cancel waiting in lock manager
5 CS 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 P
DELETE FROM MON$STATEMENTS does not interrupt a longish fetch
6 CS P P P P P P P P P P P P P P P P P P P F P P P P P P P P P P
Unclear gstat's diagnostic when damaged page in DB file appears encrypted
7 CS P P P P P P P P P P P P P P P P P F P P P P P P P P P P P P
Restore (without replace) when database already exists crashes gbak or Firebird (when run through service manager)
8 CS P P P P P P P P P P P F X X X X X X X X X X X X X X X X X X
When the statement timeout is set, it causes the lock manager to delay reporting deadlocks until timeout is expired
9 SS P P F P P P P P P F P P P P P P P P P P P P P P P P P P P P
DROP DATABASE lead FB to hang if it is issued while DB encrypting/decrypting is in progress
10 CS P P F X X X X X X X X X X X X X X X X X X X X X X X X X X X
Make protocol schemes case-insensitive
11 SS P P F X X X X X X X X X X X X X X X X X X X X X X X X X X X
Make protocol schemes case-insensitive
12 CS P P P P P P P P F F F P P X X X X X X X X X X X X X X X X X
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
13 SS P P P P P P P P F F F P P X X X X X X X X X X X X X X X X X
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
14 CS 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 F P F
Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set
15 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 P F P F
Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set

Elapsed time, milliseconds:

NN Test name mode median_ms 4.0.5.3100
2024-05-17
4.0.5.3098
2024-05-15
4.0.5.3092
2024-05-08
4.0.5.3091
2024-04-30
4.0.5.3089
2024-04-27
4.0.5.3088
2024-04-19
4.0.5.3086
2024-04-17
4.0.5.3083
2024-04-13
4.0.5.3082
2024-03-26
4.0.5.3081
2024-03-23
4.0.5.3080
2024-03-19
4.0.5.3078
2024-03-16
4.0.5.3077
2024-03-15
4.0.5.3066
2024-03-13
4.0.5.3065
2024-03-12
4.0.5.3064
2024-03-10
4.0.5.3062
2024-03-01
4.0.5.3061
2024-02-21
4.0.5.3059
2024-02-18
4.0.5.3058
2024-02-13
4.0.5.3057
2024-02-12
4.0.5.3056
2024-02-11
4.0.5.3055
2024-02-10
4.0.5.3054
2024-02-04
4.0.5.3053
2024-01-30
4.0.5.3052
2024-01-26
4.0.5.3051
2024-01-25
4.0.5.3050
2024-01-15
4.0.5.3049
2023-12-30
4.0.5.3045
2023-12-21
Test TITLE
1 CS 2108 2079 5025 2091 2260 2103 2111 2483 2072 2076 2374 2084 2030 2098 2101 2390 2101 2086 2175 2190 2142 2110 2095 2380 2131 2100 2223 2191 2106 2166 2106
Count ( DISTINCT ... ) is too slow
2 CS 24750 23895 106048 23903 24719 25028 23698 24461 23837 24717 23759 24314 23312 25777 24650 24387 24858 24719 24861 24951 24781 25302 24869 27829 24698 24854 25233 25061 25180 25553 23951
Compress Data over the Network
3 SS 23910 24508 107865 23851 23105 24270 24155 25779 23679 23140 23045 23264 23999 23398 24559 24701 23416 23745 23449 24456 23727 23487 23499 24538 23531 24217 24136 23998 23500 23969 24089
Compress Data over the Network
4 SS 5890 6031 11697 5882 5889 5901 5883 6098 6039 5890 5891 5873 5846 5879 5871 5865 5869 5884 5883 5864 5880 5943 5901 5910 5892 6176 5890 5915 6303 5938 6214
Ability to cancel waiting in lock manager
5 CS 1140 1195 39640 1106 1130 1102 1119 1101 1197 1097 1155 1188 977 1078 1152 1180 1178 1137 1139 1141 1027 1209 1141 1111 1096 1104 1189 1161 1180 1180 1123
DELETE FROM MON$STATEMENTS does not interrupt a longish fetch
6 CS 2541 2532 4646 2658 2578 2526 2616 2690 2534 2533 2615 2548 2942 2833 2662 2631 2883 2627 2552 2550 1107 693 701 713 769 704 720 773 744 717 762
Unclear gstat's diagnostic when damaged page in DB file appears encrypted
7 CS 1480 1478 3478 1458 1461 1411 1489 1434 1484 1415 1507 1463 1327 1482 1504 1493 1497 1456 1867 1415 1578 1492 1426 1512 1503 1432 1492 1459 1497 1417 1384
Restore (without replace) when database already exists crashes gbak or Firebird (when run through service manager)
8 CS 21571 21570 21639 21572 21564 21563 21801 21605 21593 21565 21570 21559 21843 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
When the statement timeout is set, it causes the lock manager to delay reporting deadlocks until timeout is expired
9 SS 3625 3588 7557 5846 3578 3668 3570 3554 3811 3642 5677 3624 3492 3621 3679 3616 3856 3627 3671 3615 3583 3639 3560 3688 3611 3528 3869 3765 3526 3751 3546
DROP DATABASE lead FB to hang if it is issued while DB encrypting/decrypting is in progress
10 CS 3175 2305 3175 3300 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Make protocol schemes case-insensitive
11 SS 1564 1490 1564 1951 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Make protocol schemes case-insensitive
12 CS 5981 5750 5981 5768 5716 5768 5692 6770 5817 69474 69639 69403 13789 13987 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
13 SS 7118 6161 6212 7137 6120 6146 6162 6145 7118 68867 68714 68891 14150 13184 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
14 CS 13000 12970 13219 13968 12907 12916 13925 13990 13412 13008 12982 12939 12810 13059 12971 13969 12992 12953 12945 12919 12970 13998 12970 12971 13039 12982 13071 13086 66968 13077 66899
Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set
15 SS 13260 13400 13306 13245 14279 13258 12244 13247 13228 13289 13245 13262 13180 14359 13257 13265 13271 13239 13319 13236 13254 13267 13230 13267 13240 13239 13267 13254 66498 13267 66448
Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set

List of tests in this report:


http://tracker.firebirdsql.org/browse/core-214
http://tracker.firebirdsql.org/browse/core-3323
http://tracker.firebirdsql.org/browse/core-3977
http://tracker.firebirdsql.org/browse/core-5501
http://tracker.firebirdsql.org/browse/core-5771
http://tracker.firebirdsql.org/browse/core-733
https://github.com/FirebirdSQL/firebird-qa/tree/master/tests/functional/replication/test_bugcheck_in_rw_replica_after_conflicting_insert.py
https://github.com/FirebirdSQL/firebird-qa/tree/master/tests/functional/replication/test_invalid_msg_if_target_db_has_no_replica_flag.py
https://github.com/FirebirdSQL/firebird/issues/6802
https://github.com/FirebirdSQL/firebird/issues/7200
https://github.com/FirebirdSQL/firebird/issues/8066

=== end of list ===