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 (2 rows)
[CURRENT] 06. Has fails: tests with at least one fail for previous 30 runs (14 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 (1 rows)
10. All tests: outcomes for previous 30 runs (2389 rows)
11. All tests: durations for previous 30 runs (4647 rows)
12. Skipped: tests which was intentionally excluded from execution (66 rows)

Generated 26.03.2024 08:15
Tested: FB40.   Build: 4.0.5.3082;   SS: 26.03.24 06:34:48 - 26.03.24 07:18:45;   CS: 26.03.24 07:19:24 - 26.03.24 08:14:39;
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.1; Firebird.Qa: 0.19.1

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.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
4.0.5.3041
2023-12-19
4.0.5.3040
2023-12-12
4.0.5.3038
2023-12-03
4.0.5.3033
2023-11-30
4.0.5.3032
2023-11-28
4.0.5.3031
2023-11-25
4.0.4.3023
2023-11-21
Test TITLE
1 CS P P P P F P P P P P F P P P P P P P P P P P P P P F P P P P
Compress Data over the Network
2 SS 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 P P
Compress Data over the Network
3 CS 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 P P P P P
Unclear gstat's diagnostic when damaged page in DB file appears encrypted
4 CS P P P 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
Restore (without replace) when database already exists crashes gbak or Firebird (when run through service manager)
5 CS P 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
When the statement timeout is set, it causes the lock manager to delay reporting deadlocks until timeout is expired
6 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
DROP DATABASE lead FB to hang if it is issued while DB encrypting/decrypting is in progress
7 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 P F X
Crash potentially caused by BETWEEN Operator
8 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 P F X
Crash potentially caused by BETWEEN Operator
9 CS F F F P P 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
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
10 SS F F F P P 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
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
11 CS P P P P P P P P P P P P P P P P P P P F P F F F F F F P 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
12 SS P P P P P P P P P P P P P P P P P P P F P F F F F F F P 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
13 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 F P P P P P
Crash or hang while shutting down the replica database if segments are being applied
14 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 F P P P P P
Crash or hang while shutting down the replica database if segments are being applied

Elapsed time, milliseconds:

NN Test name mode median_ms 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
4.0.5.3041
2023-12-19
4.0.5.3040
2023-12-12
4.0.5.3038
2023-12-03
4.0.5.3033
2023-11-30
4.0.5.3032
2023-11-28
4.0.5.3031
2023-11-25
4.0.4.3023
2023-11-21
Test TITLE
1 CS 24718 24717 23759 24314 23312 25777 24650 24387 24858 24719 24861 24951 24781 25302 24869 27829 24698 24854 25233 25061 25180 25553 23951 24232 23781 23776 24252 24217 24556 25095 24666
Compress Data over the Network
2 SS 23629 23140 23045 23264 23999 23398 24559 24701 23416 23745 23449 24456 23727 23487 23499 24538 23531 24217 24136 23998 23500 23969 24089 24457 23173 24113 23269 23099 23761 23413 23059
Compress Data over the Network
3 CS 759 2533 2615 2548 2942 2833 2662 2631 2883 2627 2552 2550 1107 693 701 713 769 704 720 773 744 717 762 717 756 701 688 704 724 701 693
Unclear gstat's diagnostic when damaged page in DB file appears encrypted
4 CS 1457 1415 1507 1463 1327 1482 1504 1493 1497 1456 1867 1415 1578 1492 1426 1512 1503 1432 1492 1459 1497 1417 1384 1338 1430 1398 1342 1329 1482 1369 1332
Restore (without replace) when database already exists crashes gbak or Firebird (when run through service manager)
5 CS 21567 21565 21570 21559 21843 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
When the statement timeout is set, it causes the lock manager to delay reporting deadlocks until timeout is expired
6 SS 3615 3642 5677 3624 3492 3621 3679 3616 3856 3627 3671 3615 3583 3639 3560 3688 3611 3528 3869 3765 3526 3751 3546 3852 3576 3509 3401 3376 3431 3402 3386
DROP DATABASE lead FB to hang if it is issued while DB encrypting/decrypting is in progress
7 CS 480 478 487 525 452 528 473 481 475 472 479 464 543 491 476 472 481 483 472 495 479 489 472 480 482 485 479 478 483 877 0
Crash potentially caused by BETWEEN Operator
8 SS 324 327 349 318 312 321 363 341 312 305 329 326 328 324 329 318 315 330 355 323 313 320 317 314 327 330 319 315 327 741 0
Crash potentially caused by BETWEEN Operator
9 CS 69403 69474 69639 69403 13789 13987 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
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
10 SS 68714 68867 68714 68891 14150 13184 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
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
11 CS 13049 13008 12982 12939 12810 13059 12971 13969 12992 12953 12945 12919 12970 13998 12970 12971 13039 12982 13071 13086 66968 13077 66899 66988 66944 36886 66588 66942 12499 13437 67094
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 SS 13267 13289 13245 13262 13180 14359 13257 13265 13271 13239 13319 13236 13254 13267 13230 13267 13240 13239 13267 13254 66498 13267 66448 66423 66450 36887 66422 66458 13555 13537 66442
Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set
13 CS 14012 13901 14057 13808 13582 14075 13869 13858 14307 13240 13481 14267 13700 13864 14288 13875 13912 13960 14052 14207 14093 13497 14137 13973 14173 11922 14068 14362 16832 16765 16799
Crash or hang while shutting down the replica database if segments are being applied
14 SS 13705 13393 14195 13690 13742 13883 13394 14220 14086 13419 13403 13738 13984 13595 13374 15059 13417 13583 13679 14294 14041 13013 14077 13721 13065 15122 14056 13503 14491 13272 13237
Crash or hang while shutting down the replica database if segments are being applied

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-qa/tree/master/tests/functional/replication/test_shutdown_during_applying_segments_leads_to_crash.py
https://github.com/FirebirdSQL/firebird/issues/6802
https://github.com/FirebirdSQL/firebird/issues/7200
https://github.com/FirebirdSQL/firebird/issues/7860

=== end of list ===