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 (3 rows)
04. NEW ERRORS: tests which raised runtime error for LAST run (0 rows)
[CURRENT] 04. STILL FAILS: tests which fail for at least TWO LAST runs (7 rows)
05. NEW SLOWDOWN: tests with performance problem for LAST 5 runs (26 rows)
06. STILL SLOWDOWN: tests with performance problem for MORE THAN 5 last runs (50 rows)
07. Has fails: tests with at least one fail for previous 30 runs (59 rows)
08. Has runtime errors: tests with at least one runtime error for previous 30 runs (0 rows)
09. Has crashes/bugchecks: tests that caused FB abnormal termination for previous 30 runs (0 rows)
10. NEW PASSED: successful tests for last run and outcome = FAIL/ERROR/SKIPPED or absent previously (2 rows)
11. All tests: outcomes for previous 30 runs (2672 rows)
12. Skipped: tests which was intentionally excluded from execution (80 rows)

Generated UTC 25.04.2025 01:08
Tested: FB60.   Build / date: 6.0.0.745-78ad8660 / 2025.04.21;
Test machine: Linux 6.11.5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.11.5-1 (2024-10-27); logical CPUs: 2; RAM: 7 Gb 
QA software: Python: 3.11.9; pytest: 7.4.4; firebird.driver: 1.10.9; firebird.Qa: 0.19.3 
Jump to the list of unique test names from this report
Jump to the list with last developing commits information

Tests which fail for at least TWO last runs:

NN Test name mode
6.0.0.745
2025.04.21
6.0.0.744
2025.04.19
6.0.0.742
2025.04.17
6.0.0.737
2025.04.16
6.0.0.736
2025.04.14
6.0.0.735
2025.04.13
6.0.0.734
2025.04.12
6.0.0.730
2025.04.11
6.0.0.726
2025.04.10
6.0.0.725
2025.04.09
6.0.0.722
2025.04.08
6.0.0.719
2025.04.06
6.0.0.717
2025.04.04
6.0.0.716
2025.04.03
6.0.0.715
2025.04.02
6.0.0.710
2025.04.01
6.0.0.708
2025.03.31
6.0.0.707
2025.03.28
6.0.0.698
2025.03.26
6.0.0.693
2025.03.24
6.0.0.687
2025.03.22
6.0.0.686
2025.03.20
6.0.0.685
2025.03.19
6.0.0.680
2025.03.18
6.0.0.677
2025.03.16
6.0.0.676
2025.03.15
6.0.0.673
2025.03.13
6.0.0.671
2025.03.12
6.0.0.663
2025.03.11
6.0.0.661
2025.03.07
Test TITLE
1 CS F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F
Success message when connecting to tiny trash database file
2 SS F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F
Success message when connecting to tiny trash database file
3 CS F F F F F F F F F F F F F F F F F F P F F P P P P P P P P P
IN/ANY/ALL predicates may cause sub-optimal (late filtering) execution of joins
4 SS F F F F F F F F F F F F F F F F F F P F F P P P P P P P P P
IN/ANY/ALL predicates may cause sub-optimal (late filtering) execution of joins
5 CS F F F F F P P F P F P F F F F F P P P F P P P P P P P P F P
Services manager breaks long lines into 1023 bytes portions when using isc_info_svc_line in Service::query()
6 CS F F F 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
SubQueryConversion = true: error "no current record for fetch operation" with complex joins
7 SS F F F 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
SubQueryConversion = true: error "no current record for fetch operation" with complex joins

Elapsed time, milliseconds:

NN Test name mode median_ms
6.0.0.745
2025.04.21
6.0.0.744
2025.04.19
6.0.0.742
2025.04.17
6.0.0.737
2025.04.16
6.0.0.736
2025.04.14
6.0.0.735
2025.04.13
6.0.0.734
2025.04.12
6.0.0.730
2025.04.11
6.0.0.726
2025.04.10
6.0.0.725
2025.04.09
6.0.0.722
2025.04.08
6.0.0.719
2025.04.06
6.0.0.717
2025.04.04
6.0.0.716
2025.04.03
6.0.0.715
2025.04.02
6.0.0.710
2025.04.01
6.0.0.708
2025.03.31
6.0.0.707
2025.03.28
6.0.0.698
2025.03.26
6.0.0.693
2025.03.24
6.0.0.687
2025.03.22
6.0.0.686
2025.03.20
6.0.0.685
2025.03.19
6.0.0.680
2025.03.18
6.0.0.677
2025.03.16
6.0.0.676
2025.03.15
6.0.0.673
2025.03.13
6.0.0.671
2025.03.12
6.0.0.663
2025.03.11
6.0.0.661
2025.03.07
Test TITLE
1 CS 1295 1295 1344 1203 1364 1115 1276 1012 1296 635 1129 1347 1182 1189 1335 1276 1361 571 1076 1278 1381 1447 1381 1423 986 1550 1025 1562 1508 1437 1322
Success message when connecting to tiny trash database file
2 SS 548 579 562 617 577 514 448 461 436 442 372 599 528 546 570 527 478 460 510 543 578 348 582 540 551 571 597 607 585 636 604
Success message when connecting to tiny trash database file
3 CS 1126 1116 917 874 827 1470 1404 1512 1170 807 1380 935 1482 1518 922 1000 882 1420 1067 2075 1525 934 1381 880 792 1140 897 1112 1136 1155 1197
IN/ANY/ALL predicates may cause sub-optimal (late filtering) execution of joins
4 SS 610 620 708 628 673 573 613 571 633 586 608 624 519 632 633 629 661 605 583 563 613 687 664 638 463 456 468 504 428 437 479
IN/ANY/ALL predicates may cause sub-optimal (late filtering) execution of joins
5 CS 3106 3129 3160 3112 3595 3028 3084 3116 3082 3147 3060 3161 3132 3065 3057 3130 3191 3100 3084 3986 3191 3128 3631 3664 710 1078 811 1071 638 691 617
Services manager breaks long lines into 1023 bytes portions when using isc_info_svc_line in Service::query()
6 CS 951 739 1204 709 1163 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
SubQueryConversion = true: error "no current record for fetch operation" with complex joins
7 SS 746 762 639 730 1202 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
SubQueryConversion = true: error "no current record for fetch operation" with complex joins

List of tests in this report:


http://tracker.firebirdsql.org/browse/CORE-2484
http://tracker.firebirdsql.org/browse/CORE-5236
https://github.com/FirebirdSQL/firebird/issues/7141
https://github.com/FirebirdSQL/firebird/issues/8223
=== end of list ===

Last commits information (all timestamps in UTC):