Skip to content

Conversation

@danxuliu
Copy link
Member

Backport of #20470

I have kept the settings/js/apps.js entry in tests/karma.config.js as it is a valid path in stable16 (although it does not seem to have any effect on the tests, though).

The build/package-lock.json was also updated, although it is worth noting that it is ignored when the tests are run in Drone, as nextcloudci/jsunit:jsunit-5 is still using npm 3.10.8 and back then there was no support yet for package-lock files (it was introduced in NPM 5 if I recall correctly).

JSUnit tests are failing for some reason. It seems to be related to a new karma-coverage version published a few hours ago.

Signed-off-by: Daniel Kesselberg <[email protected]>
@MorrisJobke MorrisJobke merged commit 46b9c8e into stable16 Apr 23, 2020
@MorrisJobke MorrisJobke deleted the backport/20470/stable16-fix/noid/karma-coverage branch April 23, 2020 20:07
@MorrisJobke MorrisJobke added this to the Nextcloud 16.0.11 milestone Apr 23, 2020
@rullzer rullzer mentioned this pull request May 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants