Visitar URL original
Failed acceptance tests for encryption and OC11 · Issue #41463 · owncloud/core · GitHub
Skip to content

Failed acceptance tests for encryption and OC11 #41463

Open

Description

@jvillafanez

Several acceptance tests have web timeouts causing failures.

    /var/www/owncloud/testrunner/tests/acceptance/features/webUIRestrictSharing/restrictSharing.feature:64
    /var/www/owncloud/testrunner/tests/acceptance/features/webUIRestrictSharing/restrictSharing.feature:79
    /var/www/owncloud/testrunner/tests/acceptance/features/webUIRestrictSharing/restrictSharing.feature:64
    /var/www/owncloud/testrunner/tests/acceptance/features/webUIRestrictSharing/restrictSharing.feature:79

runsh: Total unexpected failed scenarios throughout the test run:
webUIRestrictSharing/restrictSharing.feature:64
webUIRestrictSharing/restrictSharing.feature:79

It's unclear if the where the errors come from. Manual tests doesn't trigger the error and shows the expected test result.

For the short term those 2 affected tests will be skipped until further investigation.

Steps to reproduce

Expected behaviour

Tell us what should happen

Actual behaviour

Tell us what happens instead

Server configuration

Operating system:

Web server:

Database:

PHP version:

ownCloud version: (see ownCloud admin page)

Updated from an older ownCloud or fresh install:

Where did you install ownCloud from:

Signing status (ownCloud 9.0 and above):

Login as admin user into your ownCloud and access 
http://example.com/index.php/settings/integrity/failed 
paste the results into https://gist.github.com/ and puth the link here.

The content of config/config.php:

Log in to the web-UI with an administrator account and click on
'admin' -> 'Generate Config Report' -> 'Download ownCloud config report'
This report includes the config.php settings, the list of activated apps
and other details in a well sanitized form.

or 

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your ownCloud installation folder

*ATTENTION:* Do not post your config.php file in public as is. Please use one of the above
methods whenever possible. Both, the generated reports from the web-ui and from occ config:list
consistently remove sensitive data. You still may want to review the report before sending.
If done manually then it is critical for your own privacy to dilligently
remove *all* host names, passwords, usernames, salts and other credentials before posting.
You should assume that attackers find such information and will use them against your systems.

List of activated apps:

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your ownCloud installation folder.

Are you using external storage, if yes which one: local/smb/sftp/...

Are you using encryption: yes/no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...

LDAP configuration (delete this part if not used)

With access to your command line run e.g.:
sudo -u www-data php occ ldap:show-config
from within your ownCloud installation folder

Without access to your command line download the data/owncloud.db to your local
computer or access your SQL server remotely and run the select query:
SELECT * FROM `oc_appconfig` WHERE `appid` = 'user_ldap';


Eventually replace sensitive data as the name/IP-address of your LDAP server or groups.

Client configuration

Browser:

Operating system:

Logs

Web server error log

Insert your webserver log here

ownCloud log (data/owncloud.log)

Insert your ownCloud log here

Browser log

Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log 
c) ...

Activity

  1. changed the title [-]Failed acceptance tests for encryptio and OC11[/-] [+]Failed acceptance tests for encryption and OC11[/+] on Feb 20, 2026
  2. DeepDiver1975 commented on Jun 24, 2026

    @DeepDiver1975
    Contributor

    🤖 Automated issue triage by Claude Code review agent.

    This is a QA/test-infrastructure triage ticket rather than a located product defect, so triaging it as analysis-only.

    Observations:

    • Despite the title ("encryption and OC11"), the body tracks web-UI timeout failures in tests/acceptance/features/webUIRestrictSharing/restrictSharing.feature:64 and :79 — i.e. flaky acceptance-test runs, not an encryption regression.
    • The report itself states the cause is unknown ("It's unclear where the errors come from"), that manual testing does not reproduce the failure and shows the expected result, and that the two scenarios were temporarily skipped pending investigation.
    • There is no reproduction, no located code path, and no evidence of broken encryption or sharing behavior in the product — the signal is a CI timeout, which points to test-harness flakiness rather than a regression.

    Current state of the affected tests on master:

    • webUIRestrictSharing/restrictSharing.feature still exists and the webUIRestrictSharing suite is still wired up in CI (tests/acceptance/config/behat.php and .drone.star), and the two scenarios are no longer carried as skipped — so the temporary skip appears to have been lifted and the suite is running normally again.

    Conclusion: this looks like a transient/flaky acceptance-test timeout that was worked around at the time by skipping the two scenarios; there is no reproducible product bug to fix here. If these scenarios are still flaking in current CI, the right follow-up is a fresh report capturing the actual failing run/log (browser/network log at the timeout) so the timeout can be pinned to a specific step. Otherwise this can be closed as a stale QA-triage item.

  3. dj4oC commented on Jul 8, 2026

    @dj4oC
    Contributor

    Triage:

    • Title/content mismatch: title says "encryption and OC11" but the body describes webUIRestrictSharing acceptance-test timeouts — a sharing-flow flake, not encryption. Recommend a maintainer retitle this to avoid misrouting (e.g. to the encryption backlog) — not renaming it myself since that's a content judgment call, not a mechanical fix.
    • Component: sharing (per actual content), related to webUI Public Link sharing scenario intermittent failures #41492 (same flaky-acceptance-test class).
    • Severity: low.
    • Labels applied per actual content: Type:Bug, feature:sharing, QA:team.

    🤖 Automated review by Claude Code (security · stability · performance · coverage)


    Generated by Claude Code

  4. dj4oC commented on Jul 8, 2026

    @dj4oC
    Contributor

    Correction: the label-apply call in my previous comment actually failed (403 Resource not accessible by integration — this bot's GitHub App token doesn't have label-write permission on this repo). Suggested labels Type:Bug, feature:sharing, QA:team were not applied; a maintainer will need to add them manually (along with considering the title correction noted above).


    Generated by Claude Code

  5. dj4oC commented on Jul 8, 2026

    @dj4oC
    Contributor

    Before this can be acted on, the following needs to be resolved:

    • Title/content mismatch: the title says "encryption and OC11" but the body only describes webUIRestrictSharing/restrictSharing.feature:64 and :79 timeout failures — please confirm which behavior this issue is meant to track, or split it.
    • No reproduction: the report states the cause is unclear and that manual testing does not reproduce the failure; without a specific failing run's log (browser/network trace at the timeout) there is no code path to investigate.
    • Current-status check needed: these two scenarios are not currently carried as skipped on master, suggesting the original timeout may already be resolved — please confirm whether it's still reproducing in current CI before keeping this open as an active bug.

    🤖 Automated by Claude Code


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions