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

Generated UTC 23.02.2025 02:23
Tested: FB60.   Build / date: 6.0.0.652-226622f2 / 2025.02.22;
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.6; 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 with result = "PASSED" after previous outcome = FAIL/ERROR/SKIPPED or absent:

NN Test name mode
6.0.0.652
2025.02.22
6.0.0.647
2025.02.21
6.0.0.640
2025.02.19
6.0.0.639
2025.02.18
6.0.0.637
2025.02.12
6.0.0.636
2025.02.11
6.0.0.635
2025.02.10
6.0.0.629
2025.02.07
6.0.0.628
2025.02.06
6.0.0.621
2025.02.05
6.0.0.609
2025.02.04
6.0.0.607
2025.02.03
6.0.0.601
2025.02.01
6.0.0.600
2025.01.27
6.0.0.599
2025.01.25
6.0.0.598
2025.01.23
6.0.0.595
2025.01.22
6.0.0.594
2025.01.21
6.0.0.590
2025.01.20
6.0.0.588
2025.01.19
6.0.0.587
2025.01.18
6.0.0.585
2025.01.16
6.0.0.584
2025.01.15
6.0.0.581
2025.01.15
6.0.0.581
2025.01.14
6.0.0.577
2025.01.14
6.0.0.577
2025.01.13
6.0.0.576
2025.01.12
6.0.0.573
2025.01.10
6.0.0.571
2024.12.31
Test TITLE
1 CS P F P P P P P P P P P P P P P P X X X X X X X X X X X X X X
Error message "SQL -104 / Unexpected end of command" appears in a trace log when 'SET AUTOTERM ON;' is used
2 SS P F P P P P P P P P P P P P P P X X X X X X X X X X X X X X
Error message "SQL -104 / Unexpected end of command" appears in a trace log when 'SET AUTOTERM ON;' is used

Elapsed time, milliseconds:

NN Test name mode median_ms
6.0.0.652
2025.02.22
6.0.0.647
2025.02.21
6.0.0.640
2025.02.19
6.0.0.639
2025.02.18
6.0.0.637
2025.02.12
6.0.0.636
2025.02.11
6.0.0.635
2025.02.10
6.0.0.629
2025.02.07
6.0.0.628
2025.02.06
6.0.0.621
2025.02.05
6.0.0.609
2025.02.04
6.0.0.607
2025.02.03
6.0.0.601
2025.02.01
6.0.0.600
2025.01.27
6.0.0.599
2025.01.25
6.0.0.598
2025.01.23
6.0.0.595
2025.01.22
6.0.0.594
2025.01.21
6.0.0.590
2025.01.20
6.0.0.588
2025.01.19
6.0.0.587
2025.01.18
6.0.0.585
2025.01.16
6.0.0.584
2025.01.15
6.0.0.581
2025.01.15
6.0.0.581
2025.01.14
6.0.0.577
2025.01.14
6.0.0.577
2025.01.13
6.0.0.576
2025.01.12
6.0.0.573
2025.01.10
6.0.0.571
2024.12.31
Test TITLE
1 CS 2705 2716 2720 2703 2684 2684 2702 2705 2744 2702 2706 2690 2711 2706 2710 2705 2699 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Error message "SQL -104 / Unexpected end of command" appears in a trace log when 'SET AUTOTERM ON;' is used
2 SS 2526 2521 2543 2557 2517 2972 2530 2509 2536 2505 2538 2516 2516 2522 2518 2530 2535 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Error message "SQL -104 / Unexpected end of command" appears in a trace log when 'SET AUTOTERM ON;' is used

List of tests in this report:


https://github.com/FirebirdSQL/firebird/issues/8409
=== end of list ===

Last commits information (all timestamps in UTC):