Libelektra: running unit tests is much slower

Created on 8 Aug 2018  Â·  6Comments  Â·  Source: ElektraInitiative/libelektra

Seems like one of the current changes (maybe the pluginprocessification of Python?) drastically increased the time needed to execute all tests. First I thought this is only locally but also the build server seems to suffer from the same problem:

2min https://build.libelektra.org/jenkins/blue/organizations/jenkins/libelektra/detail/master/174/pipeline/220
7min https://build.libelektra.org/jenkins/blue/organizations/jenkins/libelektra/detail/master/181/pipeline/220

Might be related to #2160

Any idea?

build help wanted usability

All 6 comments

In case its related to pluginprocess, shouldn't such tests be much slower as well locally? 2 to 7 minutes really sounds like a huge regression, the pluginprocess tests always executed almost instantly on my machine

Yes, for me it is also slower locally. Isn't it for you?

There should be artifacts in XML Format Form the Tests with time used per
test case. You can compare those to determine what takes longer.

You are also comparing builds that were done on different machines (one more powerful than the other)

e1528532 notifications@github.com schrieb am Mi., 8. Aug. 2018, 16:32:

In case its related to pluginprocess, shouldn't such tests be much slower
as well locally? 2 to 7 minutes really sounds like a huge regression, the
pluginprocess tests always executed almost instantly on my machine

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ElektraInitiative/libelektra/issues/2168#issuecomment-411427237,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEOv-nB-PAnkrZo6pDHlbqNJhxzbA_jLks5uOvZ9gaJpZM4Vzx-K
.

Seems like the testshell testcases are the one that take long. Most of them need more than 5 seconds, and the other test cases usually need much less than 1 second. But this might be related to the many keys I have locally.

I did not check for the build server.

Alternatively, the working nftw might cause the problem. Maybe there are so many files to remove?

i checked the build server log and the test execution time for both testlib_pluginprocess and testmod_python is stated as <1s. Locally these tests don't take much time either.

I am afraid the reason for this is that my local KDB is now too big. Hopefully the mmap storage will improve this.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mpranj picture mpranj  Â·  3Comments

e1528532 picture e1528532  Â·  4Comments

markus2330 picture markus2330  Â·  4Comments

markus2330 picture markus2330  Â·  4Comments

mpranj picture mpranj  Â·  3Comments