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)
04. STILL FAILS: tests which fail for at least TWO LAST runs (27 rows)
[CURRENT] 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 (50 rows)
07. Has fails: tests with at least one fail for previous 30 runs (87 rows)
08. Has runtime errors: tests with at least one runtime error for previous 30 runs (1 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 (0 rows)
11. All tests: outcomes for previous 30 runs (2594 rows)
12. Skipped: tests which was intentionally excluded from execution (80 rows)

Generated UTC 17.01.2025 11:05
Tested: HQ50.   Build / date: 5.0.2.1577-3c80e7c5 / 2024.12.24;
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.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 performance slowdown for LAST 5 runs - moving medians

LAST moving median (window = 5) greater than previous for at least 1.33x. No more than 50 rows are shown, pre-filtered in descending order of ratio between latest and previous medians:
NN Test name mode Test last update Moving medians chart
5.0.2.1577
2024.12.24
5.0.2.1576
2024.12.17
5.0.2.1575
2024.12.08
5.0.2.1567
2024.11.26
5.0.2.1567
2024.11.21
5.0.2.1567
2024.11.18
5.0.2.1533
2024.10.23
5.0.2.1533
2024.10.22
5.0.2.1532
2024.10.15
5.0.2.1518
2024.10.04
5.0.2.1518
2024.09.26
5.0.2.1489
2024.09.05
5.0.2.1489
2024.08.31
5.0.2.1476
2024.08.09
5.0.1.1454
2024.08.08
5.0.1.1453
2024.08.06
5.0.1.1453
2024.07.30
5.0.1.1453
2024.07.28
5.0.1.1429
2024.07.19
5.0.1.1428
2024.07.15
5.0.1.1428
2024.06.30
5.0.1.1415
2024.06.11
X X X X
Test TITLE
1 SS 2022.02.02 14:46
7 5 5 6 6 6 6 6 6 6 11 11 11 11 9 9 9 9 X X X X X X X X
Cannot CREATE VIEW that selects from a system table, despite having all grants
2 CS 2022.02.02 14:46
8 6 6 6 8 7 7 7 7 7 9 10 10 9 9 7 7 7 X X X X X X X X
Error "no current record for fetch operation" is raised while deleting record from MON$ATTACHMENTS using ORDER BY clause
3 SS 2023.10.07 07:48
8 6 5 5 5 5 5 6 7 7 7 8 8 5 5 7 7 8 X X X X X X X X
CREATE DOMAIN - CHECK
4 CS 2024.06.21 10:50
47421 27196 26732 26659 26659 26659 26659 26659 27363 27363 29720 29720 29720 29706 29692 29677 29645 29163 X X X X X X X X
Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set
5 SS 2024.06.21 10:50
46325 27030 26536 25765 24378 23991 23991 24378 26968 28210 28210 28210 27398 27103 26763 26763 26621 26043 X X X X X X X X
Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set

Elapsed time, milliseconds:

NN Test name mode
5.0.2.1577
2024.12.24
5.0.2.1576
2024.12.17
5.0.2.1575
2024.12.08
5.0.2.1567
2024.11.26
5.0.2.1567
2024.11.21
5.0.2.1567
2024.11.18
5.0.2.1533
2024.10.23
5.0.2.1533
2024.10.22
5.0.2.1532
2024.10.15
5.0.2.1518
2024.10.04
5.0.2.1518
2024.09.26
5.0.2.1489
2024.09.05
5.0.2.1489
2024.08.31
5.0.2.1476
2024.08.09
5.0.1.1454
2024.08.08
5.0.1.1453
2024.08.06
5.0.1.1453
2024.07.30
5.0.1.1453
2024.07.28
5.0.1.1429
2024.07.19
5.0.1.1428
2024.07.15
5.0.1.1428
2024.06.30
5.0.1.1415
2024.06.11
X X X X X X X X
Test TITLE
1 SS 8 7 5 7 5 5 6 8 8 5 6 6 20 12 11 7 6 11 9 9 11 9 X X X X X X X X
Cannot CREATE VIEW that selects from a system table, despite having all grants
2 CS 10 5 9 6 8 5 5 10 12 7 6 6 20 11 9 10 9 6 7 7 14 7 X X X X X X X X
Error "no current record for fetch operation" is raised while deleting record from MON$ATTACHMENTS using ORDER BY clause
3 SS 8 6 5 8 8 5 5 5 5 7 6 7 10 10 5 8 5 5 9 7 11 8 X X X X X X X X
CREATE DOMAIN - CHECK
4 CS 47421 56198 49053 27196 26732 26260 26269 26659 27659 26659 26115 27363 32368 44040 29720 29677 29706 29692 29110 29163 29645 26669 X X X X X X X X
Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set
5 SS 46325 49568 47475 27030 26536 25765 23895 24378 23991 20507 26968 28210 30382 41257 23288 27398 27103 23582 26763 26043 26621 25684 X X X X X X X X
Invalid message in replication.log (and possibly crash in the case of synchronous replication) when the target DB has no its "replica" flag set

List of tests in this report:


http://tracker.firebirdsql.org/browse/CORE-5060
http://tracker.firebirdsql.org/browse/CORE-5684
https://github.com/FirebirdSQL/firebird-qa/tree/master/tests/functional/domain/create/test_38.py
https://github.com/FirebirdSQL/firebird-qa/tree/master/tests/functional/replication/test_invalid_msg_if_target_db_has_no_replica_flag.py
=== end of list ===

Last commits information (all timestamps in UTC):