Description of problem
As number of log messages in test increases, beakerlib gets slower and slower. It has been explained to me by jprokes that this is caused by beakerlib repeatedly parsing/writing the whole XML, which naturally takes longer as the XML is bigger.
This causes a lot of resource wastage with longer tests.
Version-Release number of selected component
Always, with longer tests.
Steps to Reproduce
1. Have a test with hundreds of log messages and asserts
2. Observe logging efficiency over the course of the test
The efficiency goes down as existing log is longer.
The efficiency is the same.
I have a test which runs by traversing 120 cases; with each iteration generates about 150 log messages (~50 rlLog* calls) or asserts in 5 phases. The actual payload is roughly the same in each case (add/remove 1-2 users, edit few files, restart services...).
Today I added some time measurements: The first iteration takes roughly 3.5 seconds and this number steadily grows larger and larger up to 17 seconds at the last iteration! My calculations: If each iteration took 4 seconds, the whole test would take 8 minutes, but really it takes 20.
IOW, the "beakerlib tax" comes to more than double the final test time.
This is known issue. It is caused by current journaling.py which rebuilds journal.xml every time it writes anything. It is not an easy job to fix it properly.
If you are willing to participate on this you are more then welcome.
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.