Enable full smashbox test execution with encryption enabled on CI

[LukasReschke]

While coding #21557 it has been discovered (#22125) that smashbox has been broken on master with encryption enabled. There was effectively a case where users were not able to access their files.

This has been fixed by @PVince81 meanwhile with #22220. But considering that we only discovered this due to explicitly testing encryption ourselves we should certainly have smashbox executed on CI as well with encryption enabled. (not on the PRs probably but on the daily builds?)

cc @MorrisJobke @PVince81 As discussed.
cc @karlitschek @DeepDiver1975 Thoughts?

[LukasReschke]

Tentatively assigning our great @owncloud-bot master @DeepDiver1975.

[PVince81]

Beware: smashbox with encryption might need more disk space due to bigger files, so make sure to check the logs for InsufficientStorage in case it fails.

[karlitschek]

i agree. ideally we should run all the tests with and without encryption. not sure if this doable with our current hardware

[DeepDiver1975]

AFAIK there is a docker available which allows tests with encryption enabled - let me see what I can do these days ....

[DeepDiver1975]

moved to backlog once we have ci back into shape

[ownclouders]

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)