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 (14 rows)
[CURRENT] 05. NEW SLOWDOWN: tests with performance problem for LAST 5 runs (1 rows)
06. STILL SLOWDOWN: tests with performance problem for MORE THAN 5 last runs (30 rows)
07. Has fails: tests with at least one fail for previous 30 runs (43 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 (1 rows)
11. All tests: outcomes for previous 30 runs (2445 rows)
12. Skipped: tests which was intentionally excluded from execution (75 rows)

Generated UTC 17.02.2025 08:05
Tested: HQ40.   Build / date: 4.0.6.3183-cf6ca3ce / 2025.02.16;
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.5x. 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
4.0.6.3183
2025.02.16
4.0.6.3169
2024.12.13
4.0.6.3169
2024.12.08
4.0.6.3168
2024.11.28
4.0.6.3163
2024.10.16
4.0.6.3163
2024.10.15
4.0.6.3147
2024.08.31
4.0.6.3140
2024.08.16
4.0.6.3140
2024.08.09
4.0.5.3110
2024.07.30
4.0.5.3109
2024.06.11
4.0.5.3097
2024.05.09
4.0.5.3091
2024.04.29
4.0.5.3089
2024.04.25
X X X X X X X X X X X X
Test TITLE
1 SS 2024.06.21 10:50
49722 32633 32633 32633 34273 34273 35394 35394 33559 33447 X X X X X X X X 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
4.0.6.3183
2025.02.16
4.0.6.3169
2024.12.13
4.0.6.3169
2024.12.08
4.0.6.3168
2024.11.28
4.0.6.3163
2024.10.16
4.0.6.3163
2024.10.15
4.0.6.3147
2024.08.31
4.0.6.3140
2024.08.16
4.0.6.3140
2024.08.09
4.0.5.3110
2024.07.30
4.0.5.3109
2024.06.11
4.0.5.3097
2024.05.09
4.0.5.3091
2024.04.29
4.0.5.3089
2024.04.25
X X X X X X X X X X X X X X X X
Test TITLE
1 SS 49855 49722 49746 30292 32633 26783 34273 60556 35394 33447 35792 33559 30237 33253 X X X X X X X X 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:


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):