Uh oh!
There was an error while loading. Please reload this page.
[stable20] Remove stray compiled assets - #25480
Conversation
This was automatically deleted and not regenerated by: make dev-setup && make build-js-production Signed-off-by: Vincent Petry <vincent@nextcloud.com>
PVince81
commented
Feb 4, 2021
I've had a quick test of the users page and it seemed to work fine. The matching acceptance tests will also confirm this. |
PVince81
commented
Feb 5, 2021
restarted CI for hopefully slightly greener results |
ChristophWurst
left a comment
There was a problem hiding this comment.
Had to do the same in another PR
juliusknorr
commented
Feb 5, 2021
Yes, the settings chunk names are chaning on every build update so they maybe a not cleaned up build has made it to the base branch. |
juliusknorr
commented
Feb 5, 2021
Actually we should have #24865 for stable20 as well |
🤖 beep boop beep 🤖 Here are the logs for the failed build: Status of 1950: failureacceptance-app-files-sharing
Show full log |
PVince81
commented
Feb 5, 2021
failures seem unrelated: both in acceptance tests for sharing |
PVince81
commented
Feb 5, 2021
I've raised #25491 to look into the failed sharing acceptance test as it seems to happen consistently on stable20. |
This was automatically deleted and not regenerated by:
make dev-setup && make build-js-production
I ran those on stable20 and committed the result.
I didn't see this happen on stable21 or master, so probably it's assets that exist since a while and were never properly deleted.
Also: CI did not complain about those missing.
Removing these will avoid devs to be confused like I was in #25475 especially when changing seemingly related files.