win-5x new_failed

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)
[CURRENT] 03. NEW FAILS: tests which failed for LAST run (1 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)
06. Has fails: tests with at least one fail for previous 30 runs (20 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 (2 rows)
10. All tests: outcomes for previous 30 runs (2513 rows)
11. All tests: durations for previous 30 runs (4860 rows)
12. Skipped: tests which was intentionally excluded from execution (69 rows)

Generated 15.06.2024 06:30
Tested: FB50. Build: 5.0.1.1416; SS: 15.06.24 04:53:22 - 15.06.24 05:35:51; CS: 15.06.24 05:36:32 - 15.06.24 06:29: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.4; Firebird.Qa: 0.19.3

Tests with result = "FAIL" for last run:

Jump to LIST of unique test names from this report

NN	Test name	mode	5.0.1.1416 2024-06-15	5.0.1.1415 2024-06-13	5.0.1.1412 2024-06-09	5.0.1.1411 2024-06-06	5.0.1.1408 2024-05-29	5.0.1.1405 2024-05-22	5.0.1.1404 2024-05-21	5.0.1.1399 2024-05-15	5.0.1.1398 2024-05-14	5.0.1.1395 2024-05-08	5.0.1.1394 2024-05-06	5.0.1.1393 2024-05-02	5.0.1.1392 2024-04-30	5.0.1.1391 2024-04-29	5.0.1.1390 2024-04-27	5.0.1.1389 2024-04-26	5.0.1.1387 2024-04-25	5.0.1.1386 2024-04-21	5.0.1.1383 2024-04-19	5.0.1.1381 2024-04-17	5.0.1.1379 2024-04-13	5.0.1.1378 2024-04-10	5.0.1.1377 2024-04-04	5.0.1.1375 2024-04-03	5.0.1.1373 2024-04-02	5.0.1.1372 2024-03-26	5.0.1.1371 2024-03-23	5.0.1.1370 2024-03-21	5.0.1.1369 2024-03-19	5.0.1.1368 2024-03-16	Test TITLE
1	bugs gh 6802 tracker	SS	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	F	When the statement timeout is set, it causes the lock manager to delay reporting deadlocks until timeout is expired

Elapsed time, milliseconds:

NN	Test name	mode	median_ms	5.0.1.1416 2024-06-15	5.0.1.1415 2024-06-13	5.0.1.1412 2024-06-09	5.0.1.1411 2024-06-06	5.0.1.1408 2024-05-29	5.0.1.1405 2024-05-22	5.0.1.1404 2024-05-21	5.0.1.1399 2024-05-15	5.0.1.1398 2024-05-14	5.0.1.1395 2024-05-08	5.0.1.1394 2024-05-06	5.0.1.1393 2024-05-02	5.0.1.1392 2024-04-30	5.0.1.1391 2024-04-29	5.0.1.1390 2024-04-27	5.0.1.1389 2024-04-26	5.0.1.1387 2024-04-25	5.0.1.1386 2024-04-21	5.0.1.1383 2024-04-19	5.0.1.1381 2024-04-17	5.0.1.1379 2024-04-13	5.0.1.1378 2024-04-10	5.0.1.1377 2024-04-04	5.0.1.1375 2024-04-03	5.0.1.1373 2024-04-02	5.0.1.1372 2024-03-26	5.0.1.1371 2024-03-23	5.0.1.1370 2024-03-21	5.0.1.1369 2024-03-19	5.0.1.1368 2024-03-16	Test TITLE
1	bugs gh 6802 tracker	SS	21359	21342	21379	21339	21359	21346	21361	21343	21450	21373	21359	21338	21355	21390	21367	21385	21373	21362	21345	21385	21386	21355	21341	21369	21358	21337	21367	21358	21365	21360	21343	When the statement timeout is set, it causes the lock manager to delay reporting deadlocks until timeout is expired

List of tests in this report:

https://github.com/FirebirdSQL/firebird/issues/6802

=== end of list ===