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 (2 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 (12 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 (5 rows)
10. All tests: outcomes for previous 30 runs (2401 rows)
11. All tests: durations for previous 30 runs (4661 rows)
12. Skipped: tests which was intentionally excluded from execution (66 rows)

Generated 14.05.2024 08:54
Tested: FB40.   Build: 4.0.5.3098;   SS: 14.05.24 06:59:58 - 14.05.24 07:51:56;   CS: 14.05.24 07:52:40 - 14.05.24 08:52:52;
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.3098
2024-05-14		 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		 4.0.5.3042
2023-12-20
Test TITLE
1
bugs core 0733 
 tracker
 CS 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 P
Compress Data over the Network
2
bugs core 0733 
 tracker
 SS 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 P
Compress Data over the Network
3
bugs core 5501 
 tracker
 CS 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 P
Unclear gstat's diagnostic when damaged page in DB file appears encrypted
4
bugs core 5771 
 tracker
 CS 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 P
Restore (without replace) when database already exists crashes gbak or Firebird (when run through service manager)
5
bugs gh 6802 
 tracker
 CS 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 X
When the statement timeout is set, it causes the lock manager to delay reporting deadlocks until timeout is expired
6
bugs gh 7200 
 tracker
 SS 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 P
DROP DATABASE lead FB to hang if it is issued while DB encrypting/decrypting is in progress
7
bugs gh 8066 
 tracker
 CS 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 X
Make protocol schemes case-insensitive
8
bugs gh 8066 
 tracker
 SS 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 X
Make protocol schemes case-insensitive
9
functional replication bugcheck in rw replica after conflicting insert 
 CS 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 X
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
10
functional replication bugcheck in rw replica after conflicting insert 
 SS 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 X
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
11
functional replication invalid msg if target db has no replica flag 
 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 F P F 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
12
functional replication invalid msg if target db has no replica flag 
 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 F 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.3098
2024-05-14		 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		 4.0.5.3042
2023-12-20
Test TITLE
1
bugs core 0733 
 tracker
 CS 24750 115259 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 24232
Compress Data over the Network
2
bugs core 0733 
 tracker
 SS 23910 123168 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 24457
Compress Data over the Network
3
bugs core 5501 
 tracker
 CS 2541 2659 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 717
Unclear gstat's diagnostic when damaged page in DB file appears encrypted
4
bugs core 5771 
 tracker
 CS 1472 1493 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 1338
Restore (without replace) when database already exists crashes gbak or Firebird (when run through service manager)
5
bugs gh 6802 
 tracker
 CS 21570 21569 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 0
When the statement timeout is set, it causes the lock manager to delay reporting deadlocks until timeout is expired
6
bugs gh 7200 
 tracker
 SS 3633 4898 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 3852
DROP DATABASE lead FB to hang if it is issued while DB encrypting/decrypting is in progress
7
bugs gh 8066 
 tracker
 CS 2810 2321 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 0
Make protocol schemes case-insensitive
8
bugs gh 8066 
 tracker
 SS 1748 1545 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 0
Make protocol schemes case-insensitive
9
functional replication bugcheck in rw replica after conflicting insert 
 CS 6507 6244 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 0
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
10
functional replication bugcheck in rw replica after conflicting insert 
 SS 7127 6171 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 0
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
11
functional replication invalid msg if target db has no replica flag 
 CS 13018 13029 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 66988
Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set
12
functional replication invalid msg if target db has no replica flag 
 SS 13260 13308 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 66423
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-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 ===