New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
is_not_rw_storage broken #2423
Comments
@kodebach Can you elaborate what exactly is broken in is_not_rw_storage? |
I just looked at the output of
The test prints one line for each plugin that was compiled and then exits successfully. (Should probably fail if no read-write storage plugin was found, because at least one is required for Elektra to function properly) Which has to correspond to these lines from if is_not_rw_storage; then
echo "$PLUGIN not a read-write storage"
continue
fi So |
Thank you for reporting! I agree it should fail if no plugins can be found. |
This issue also applies to |
is_not_rw_storage now checks if the output of "kdb info {plugin} provides" contains the word "storage" instead of checking if it is equal to storage. ElektraInitiative#2423
check_export did not expect the quotes around the value in the output of "kdb set". It now does. ElektraInitiative#2423
The problem with When I fixed this in my fork all of the tests that use Most of the |
If you uncomment this line:
you can run the testcase testscr_generate_data to generate the files in tests/shell/shell . Some plugins however shouldn't be tested because they are not normal read-write-storage plugins (e.g. c , cpptemplate , specload ), so you should first exclude the ones that shouldn't run.
For |
is_not_rw_storage now checks if the output of "kdb info {plugin} provides" contains the word "storage" instead of checking if it is equal to storage. ElektraInitiative#2423
check_export did not expect the quotes around the value in the output of "kdb set". It now does. ElektraInitiative#2423
is_not_rw_storage now checks if the output of "kdb info {plugin} provides" contains the word "storage" instead of checking if it is equal to storage. ElektraInitiative#2423
check_export did not expect the quotes around the value in the output of "kdb set". It now does. ElektraInitiative#2423
In the process of fixing this a few problems occured, which is why i had to exclude some plugins ( The problems are all very similar, they all boil down to the same sequence of commands:
With the The
|
You could also try this:
Some plugins might have problems with writing to stdout as well as reading from stdin, because they need to read the file out of order. |
Yes, I am doing that for |
is_not_rw_storage now checks if the output of "kdb info {plugin} provides" contains the word "storage" instead of checking if it is equal to storage. ElektraInitiative#2423
check_export did not expect the quotes around the value in the output of "kdb set". It now does. ElektraInitiative#2423
(Assigned as already agreed in #2595) |
@kodebach is it still feasible that you solve this issue? |
I'll look at #2595 and see what needs to be done.. |
is_not_rw_storage now checks if the output of "kdb info {plugin} provides" contains the word "storage" instead of checking if it is equal to storage. #2423
check_export did not expect the quotes around the value in the output of "kdb set". It now does. #2423
If this was not completely resolved by #2595 please reopen. |
Seems like this failed on master now: https://build.libelektra.org/blue/organizations/jenkins/libelektra/detail/master/242/pipeline/661 |
Only the version with the |
Thank you for looking into it. Yes, ini is about to be removed very soon. If I remove it now we will have a merge conflict with #3491. We can't cherry-pick since the commit also changes other files. @markus2330 is it ok if you resolve the conflict in your PR? |
Thank you both 🎆 @mpranj yes, it would be appreciated if you do fixes in the PR! Having a fixed master has of course the highest priority 🚀 |
Everything should be fixed now. @kodebach Can we close this issue? |
AFAIK everything is fixed |
As @kodebach reported in #2419:
The text was updated successfully, but these errors were encountered: