cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CB-13829) Fix tests that were broken since CB-13237
Date Wed, 07 Feb 2018 14:12:00 GMT


ASF GitHub Bot commented on CB-13829:

janpio commented on issue #246: CB-13829 Fix tests that were broken since CB-13237
has nothing to do with this (and is not mentioned anywhere here in this PR, is it?). 
   [This was just a commit of the release process that is documented here:
It had to be reverted as the release process was canceled as I discovered the failing tests
and breaking changes (which requires a 6.0 release instead of a 5.1 I was working on).]
   The culprit for the failing tests is in
but wasn't noticed as earlier `jasmine-node` was replaced by `jasmine` which doesn't have
the same command line params, which caused the tests to fail silently and not to be run at
all via

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Fix tests that were broken since CB-13237
> -----------------------------------------
>                 Key: CB-13829
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-windows
>    Affects Versions: 6.0.0
>            Reporter: Jan Piotrowski (Sujan)
>            Assignee: Jan Piotrowski (Sujan)
>            Priority: Major
> CB-13237 introduced a major breaking change (by default the projects built are not Windows10/UWP
and not 8.1 any more) and also broke the e2e-tests in the process (which wasn't noticed because
the running of tests was broken even before by the switch from jasmine-node to jasmine and
so CI didn'T report the test breakage).

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message