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)
04. STILL FAILS: tests which fail for at least TWO LAST runs (0 rows)
05. NEW SLOWDOWN: tests with performance problem for LAST 5 runs (4 rows)
[CURRENT] 06. STILL SLOWDOWN: tests with performance problem for MORE THAN 5 last runs (3 rows)
07. Has fails: tests with at least one fail for previous 30 runs (5 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 (2055 rows)
12. Skipped: tests which was intentionally excluded from execution (60 rows)

Generated UTC 30.06.2025 09:23
Tested: FB30.   Build / date: 3.0.13.33814-85255487 / 2025.06.21;
Test machine: Windows 10 10.0.19045; logical CPUs: 8; RAM: 31 Gb 
QA software: Python: 3.11.2; 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

Performance slowdown for more than 5 recent runs - moving medians

At least 2 recent moving medians (window = 5) greater than "normal" for at least 1.5x. No more than 50 rows are shown, pre-filtered in descending order of ratio between latest and "normal" medians:
NN Test name mode Test last update Moving medians chart
3.0.13.33814
2025.06.21
85255
3.0.13.33813
2025.06.14
222a9
3.0.13.33811
2025.05.07
16491
3.0.13.33810
2025.05.06
02b1d
3.0.13.33809
2025.05.05
4ec6d
3.0.13.33808
2025.04.18
bf513
3.0.13.33807
2025.04.14
73e94
3.0.13.33806
2025.03.26
b6cfe
3.0.13.33805
2025.03.17
98320
3.0.13.33804
2025.02.25
1439d
3.0.13.33803
2025.01.29
f1848
3.0.13.33802
2025.01.28
650bd
3.0.13.33800
2025.01.20
f20ab
3.0.13.33798
2025.01.16
0c3bb
3.0.13.33795
2024.12.23
1bf0b
3.0.13.33794
2024.10.23
e2a6b
3.0.13.33793
2024.09.02
3e627
3.0.13.33792
2024.08.30
d9f38
3.0.13.33791
2024.08.21
c8a36
3.0.13.33790
2024.08.20
3bf52
3.0.13.33789
2024.08.09
7933a
3.0.12.33787
2024.08.06
bf180
3.0.12.33784
2024.08.01
cd857
3.0.12.33779
2024.07.31
ae35d
3.0.12.33778
2024.07.21
4680d
3.0.12.33777
2024.07.19
8e912
Test TITLE
1
bugs core 2211 
 tracker
 SS 2022.02.02 14:46
781 781 327 327 339 355 339 350 350 337 337 337 337 337 337 376 799 647 685 685 684 660 660 281 281 276
Offset value for SUBSTRING from BLOB more than 32767 makes exception
2
bugs core 3311 
 tracker
 SS 2025.06.27 14:54
766 766 484 484 476 466 444 442 466 464 442 444 464 444 441 444 485 485 485 485 408 408 405 405 391 391
Error "data type unknown" while preparing UPDATE/DELETE statements with the parameterized ROWS clause
3
bugs core 6142 
 tracker
 SS 2025.06.02 09:04
2869 2822 2756 2822 2822 2756 2749 2749 1763 1763 2703 2846 2703 2927 2927 3054 2789 2961 2789 1888 1888 2033 2033 2719 2731 2858
Error "connection lost to database" could happen when application creates few local attachments (using XNET) simultaneously

Elapsed time, milliseconds:

NN Test name mode Test last update
3.0.13.33814
2025.06.21
85255
3.0.13.33813
2025.06.14
222a9
3.0.13.33811
2025.05.07
16491
3.0.13.33810
2025.05.06
02b1d
3.0.13.33809
2025.05.05
4ec6d
3.0.13.33808
2025.04.18
bf513
3.0.13.33807
2025.04.14
73e94
3.0.13.33806
2025.03.26
b6cfe
3.0.13.33805
2025.03.17
98320
3.0.13.33804
2025.02.25
1439d
3.0.13.33803
2025.01.29
f1848
3.0.13.33802
2025.01.28
650bd
3.0.13.33800
2025.01.20
f20ab
3.0.13.33798
2025.01.16
0c3bb
3.0.13.33795
2024.12.23
1bf0b
3.0.13.33794
2024.10.23
e2a6b
3.0.13.33793
2024.09.02
3e627
3.0.13.33792
2024.08.30
d9f38
3.0.13.33791
2024.08.21
c8a36
3.0.13.33790
2024.08.20
3bf52
3.0.13.33789
2024.08.09
7933a
3.0.12.33787
2024.08.06
bf180
3.0.12.33784
2024.08.01
cd857
3.0.12.33779
2024.07.31
ae35d
3.0.12.33778
2024.07.21
4680d
3.0.12.33777
2024.07.19
8e912
3.0.12.33766
2024.07.13
b5086
3.0.12.33765
2024.07.10
06f2a
3.0.12.33764
2024.06.18
4d0c0
3.0.12.33761
2024.06.17
b259d
Test TITLE
1
bugs core 2211 
 tracker
 SS 2022.02.02 14:46 869 781 860 327 327 857 326 339 871 355 331 350 327 337 337 336 830 376 337 799 856 647 685 273 684 660 273 281 273 276
Offset value for SUBSTRING from BLOB more than 32767 makes exception
2
bugs core 3311 
 tracker
 SS 2025.06.27 14:54 470 781 460 766 787 484 444 424 476 466 426 442 740 464 422 444 732 423 441 485 700 503 395 408 405 744 375 391 375 403
Error "data type unknown" while preparing UPDATE/DELETE statements with the parameterized ROWS clause
3
bugs core 6142 
 tracker
 SS 2025.06.02 09:04 2932 2905 1870 1846 2869 2822 2756 3128 2749 1763 1707 2846 1760 2703 2927 3091 1729 3054 2789 3901 1863 2961 1726 1888 2033 2731 3174 2719 2858 2896
Error "connection lost to database" could happen when application creates few local attachments (using XNET) simultaneously

List of tests in this report:


http://tracker.firebirdsql.org/browse/CORE-2211
http://tracker.firebirdsql.org/browse/CORE-3311
http://tracker.firebirdsql.org/browse/CORE-6142
=== end of list ===

Last commits information (all timestamps in UTC):