win-4x new_passed

01. Total results for each kind of outcome and server mode, for previous 35 runs
02. NEW CRASHES/BUGCHECKS: tests that caused FB abnormal termination for LAST run (2 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 (12 rows)
05. NEW SLOWDOWN: tests with performance problem for LAST 5 runs (5 rows)
06. STILL SLOWDOWN: tests with performance problem for MORE THAN 5 last runs (14 rows)
07. Has fails: tests with at least one fail for previous 35 runs (142 rows)
08. Has runtime errors: tests with at least one runtime error for previous 35 runs (746 rows)
09. Has crashes/bugchecks: tests that caused FB abnormal termination for previous 35 runs (2 rows)
[CURRENT] 10. NEW PASSED: successful tests for last run and outcome = FAIL/ERROR/SKIPPED or absent previously (4 rows)
11. All tests: outcomes for previous 35 runs (3319 rows)
12. Skipped: tests which was intentionally excluded from execution (253 rows)

Generated UTC 29.07.2025 12:50
Tested: HQ40. Build / date: 4.0.6.3222-685b73e2 / 2025.07.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.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 with result = "PASSED" after previous outcome = FAIL/ERROR/SKIPPED or absent:

NN	Test name	mode	4.0.6.3222 2025.07.22 685b7	4.0.6.3221 2025.07.15 0a02f	4.0.6.3189 2025.02.25 1a1a5	4.0.6.3184 2025.02.24 9388c	4.0.6.3183 2025.02.17 e4762	4.0.6.3169 2024.12.13 42cc1	4.0.6.3169 2024.12.08 50eb6	4.0.6.3168 2024.12.07 98d69	4.0.6.3168 2024.12.05 cee43	4.0.6.3168 2024.11.28 48149	4.0.6.3163 2024.10.30 832db	4.0.6.3163 2024.10.16 2bb10	4.0.6.3147 2024.09.10 a4d11	4.0.6.3147 2024.08.31 4655b	4.0.6.3140 2024.08.16 1dd8b	4.0.6.3140 2024.08.09 34747	4.0.5.3110 2024.08.06 f851c	4.0.5.3110 2024.07.30 c6527	4.0.5.3109 2024.06.11 6addf	4.0.5.3097 2024.05.09 27fa6	4.0.5.3091 2024.04.29 bd0aa	4.0.5.3089 2024.04.20 9eb9b	4.0.5.3083 2024.04.06 300f9	4.0.5.3052 2024.03.16 0f422	4.0.5.3052 2024.03.16 ce273	4.0.5.3052 2024.02.12 cd058	4.0.5.3052 2024.02.07 be290	4.0.5.3052 2024.02.07 6409b	4.0.5.3052 2024.02.02 bbc3f	4.0.5.3052 2024.01.26 48b7c	4.0.5.3052 2024.01.26 9a7b3	4.0.5.3049 2024.01.25 f6b9d	4.0.5.3049 2024.01.08 b67ce	4.0.5.3049 2024.01.08 97577	4.0.5.3049 2024.01.05 2d8b0	Test TITLE
1	bugs gh 8598 tracker	ALL	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	X	X	X	X	X	X	X	X	X	Don't fire referential integrity triggers if primary or unique keys haven't changed
2	bugs gh 8661 tracker	ALL	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	X	X	X	X	X	X	X	X	X	Strange output from SHOW DEPENDENCIES command on 6.0
3	bugs gh 8663 tracker	SS	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	X	X	X	X	X	X	X	X	X	Problem with restore time when DB has many indices (possible regression in 6.x)
4	bugs gh 8666 tracker	ALL	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	X	X	X	X	X	X	X	X	X	Crash after calling incorrectly parametrized request

Elapsed time, milliseconds:

NN	Test name	mode	median_ms	4.0.6.3222 2025.07.22 685b7	4.0.6.3221 2025.07.15 0a02f	4.0.6.3189 2025.02.25 1a1a5	4.0.6.3184 2025.02.24 9388c	4.0.6.3183 2025.02.17 e4762	4.0.6.3169 2024.12.13 42cc1	4.0.6.3169 2024.12.08 50eb6	4.0.6.3168 2024.12.07 98d69	4.0.6.3168 2024.12.05 cee43	4.0.6.3168 2024.11.28 48149	4.0.6.3163 2024.10.30 832db	4.0.6.3163 2024.10.16 2bb10	4.0.6.3147 2024.09.10 a4d11	4.0.6.3147 2024.08.31 4655b	4.0.6.3140 2024.08.16 1dd8b	4.0.6.3140 2024.08.09 34747	4.0.5.3110 2024.08.06 f851c	4.0.5.3110 2024.07.30 c6527	4.0.5.3109 2024.06.11 6addf	4.0.5.3097 2024.05.09 27fa6	4.0.5.3091 2024.04.29 bd0aa	4.0.5.3089 2024.04.20 9eb9b	4.0.5.3083 2024.04.06 300f9	4.0.5.3052 2024.03.16 0f422	4.0.5.3052 2024.03.16 ce273	4.0.5.3052 2024.02.12 cd058	4.0.5.3052 2024.02.07 be290	4.0.5.3052 2024.02.07 6409b	4.0.5.3052 2024.02.02 bbc3f	4.0.5.3052 2024.01.26 48b7c	4.0.5.3052 2024.01.26 9a7b3	4.0.5.3049 2024.01.25 f6b9d	4.0.5.3049 2024.01.08 b67ce	4.0.5.3049 2024.01.08 97577	4.0.5.3049 2024.01.05 2d8b0	Test TITLE
1	bugs gh 8598 tracker	CS	10400	10400	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	0	0	0	0	0	0	Don't fire referential integrity triggers if primary or unique keys haven't changed
2	bugs gh 8598 tracker	SS	8192	8192	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	0	0	0	0	0	0	Don't fire referential integrity triggers if primary or unique keys haven't changed
3	bugs gh 8661 tracker	CS	647	647	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	0	0	0	0	0	0	Strange output from SHOW DEPENDENCIES command on 6.0
4	bugs gh 8661 tracker	SS	421	421	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	0	0	0	0	0	0	Strange output from SHOW DEPENDENCIES command on 6.0
5	bugs gh 8663 tracker	SS	8064	8064	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	0	0	0	0	0	0	Problem with restore time when DB has many indices (possible regression in 6.x)
6	bugs gh 8666 tracker	CS	625	625	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	0	0	0	0	0	0	Crash after calling incorrectly parametrized request
7	bugs gh 8666 tracker	SS	415	415	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	0	0	0	0	0	0	Crash after calling incorrectly parametrized request

List of tests in this report:

https://github.com/FirebirdSQL/firebird/issues/8598
https://github.com/FirebirdSQL/firebird/issues/8661
https://github.com/FirebirdSQL/firebird/issues/8663
https://github.com/FirebirdSQL/firebird/issues/8666

=== end of list ===

Last commits information (all timestamps in UTC):