[ 
https://issues.apache.org/jira/browse/CB-14116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16499786#comment-16499786
 ] 

ASF GitHub Bot commented on CB-14116:
-------------------------------------

knight9999 opened a new pull request #615: CB-14116: improve tests using 
[email protected], adjusting timeout params and improve p…
URL: https://github.com/apache/cordova-lib/pull/615
 
 
   …lugin remove sequentially
   
   <!--
   Please make sure the checklist boxes are all checked before submitting the 
PR. The checklist
   is intended as a quick reference, for complete details please see our 
Contributor Guidelines:
   
   http://cordova.apache.org/contribute/contribute_guidelines.html
   
   Thanks!
   -->
   
   ### Platforms affected
   
   all platforms
   
   ### What does this PR do?
   
   1. For Test#022 on pkgJson.spec.js, using [email protected]
   
   2. Adjust timeout parameters in pkgJson.spec.js.
   
   3.  Fixing errors in Test#006 on platform.spec.js.
   `cordova plugin rm` spawns multiple `npm uninstall` commands simultaneously 
by `Q.all`.
   However multiple npm command simultaneously bring a following errors,
   ```
   { CordovaError: Error: npm: Command failed with exit code 254 Error output:
   npm WARN checkPermissions Missing write access to 
/tmp/e2e-test/plugin_rm_test/hello/node_modules/cordova-android/node_modules/abbrev
   npm WARN checkPermissions Missing write access to 
/tmp/e2e-test/plugin_rm_test/hello/node_modules/cordova-android/node_modules/android-versions
   ```
   Then I  update uninstall.js by using sequential promises instead of `Q.all`.
   
   
   ### What testing has been done on this change?
   
   on travis c.i. testing.
   
   ### Checklist
   - [x] [Reported an issue](http://cordova.apache.org/contribute/issues.html) 
in the JIRA database
   - [x] Commit message follows the format: "CB-3232: (android) Fix bug with 
resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform 
affected.
   - [x] Added automated test coverage as appropriate for this change.
   

----------------------------------------------------------------
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:
[email protected]


> Travis CI tests for cordova-lib 8.0.1-dev has been failing
> ----------------------------------------------------------
>
>                 Key: CB-14116
>                 URL: https://issues.apache.org/jira/browse/CB-14116
>             Project: Apache Cordova
>          Issue Type: Test
>          Components: cordova-lib
>    Affects Versions: Master
>         Environment: Travis c.i. test for Node 6, 8 and 10.
>            Reporter: Ken Naito
>            Priority: Major
>             Fix For: Master
>
>
> Travis CI tests for cordova-lib 8.0.1-dev has been failing for the following 
> three reasons.
> 1. Test#022 on pkgJson.spec.js, is still using an old iOS platform version 
> (4.3.0).
> 2. The pkgJson.spec.js timeout parameters are not enough. Due to network 
> conditions, sometimes tests and NPM randomly fails. 
> 3. Test#006 on platform.spec.js sometimes randomly fails because of missing 
> write access. Error below can be seen when running the test.
> { CordovaError: Error: npm: Command failed with exit code 254 Error output:
> npm WARN checkPermissions Missing write access to 
> /tmp/e2e-test/plugin_rm_test/hello/node_modules/cordova-android/node_modules/abbrev
> npm WARN checkPermissions Missing write access to 
> /tmp/e2e-test/plugin_rm_test/hello/node_modules/cordova-android/node_modules/android-versions
> npm WARN checkPermissions Missing write access to 
> /tmp/e2e-test/plugin_rm_test/hello/node_modules/cordova-android/node_modules/ansi
> npm WARN checkPermissions Missing write access to 
> /tmp/e2e-test/plugin_rm_test/hello/node_modules/cordova-android/node_modules/b



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to