Closed grgprarup closed 1 year ago
Could be similar to https://github.com/owncloud/files_lifecycle/issues/543 and might be due to changes in https://github.com/owncloud/core/commit/7706791af23629041ec12bbc2c9e528c54dfdb76
Currently the failure with status code 404
is occurring only in the apiUserLDAP-master
pipelines but on the apiUserLDAP-latest
pipelines the test passes with status code 500
.
Currently the failure with status code
404
is occurring only in theapiUserLDAP-master
pipelines but on theapiUserLDAP-latest
pipelines the test passes with status code500
.
which means that the problem that caused the 500 is fixed in master, which is good. you might need to skip the scenario on Oc 10.13.0, 10.13.1 (and the fixed code looks like it is in 10.13.2 release, which should soon be "latest")
https://drone.owncloud.com/owncloud/user_ldap/4748/31/5
The pipeline for "latest" that passed shows:
Fetched 10.13.1 - channel: stable - build at 2023-09-06T16:24:36+00:00 - SHA: d06b1d870377662dd9ff327485acc2d3e1991bcb
As at last night, "latest" was fetching 10.13.1. Downloading "latest" now still gives me 10.13.1 - but that will switch over some time soon.
The acceptance test is failing in scenario
apiUserLDAP/sharingLocalUserLdapUser.feature:136
withdaily master
serverBuilds: https://drone.owncloud.com/owncloud/user_ldap/4748/28/12