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

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

Github user riknoll commented on the pull request:

    https://github.com/apache/cordova-medic/pull/73#issuecomment-178801188
  
    @dblotsky I don't think there is an easy way to get the running simulator, 
so instead I am going to move the simulator choosing logic from `cordova run` 
to medic and pass the `--target` flag. I'll probably just do the same thing as 
above, which is choosing the last iPhone that appears in the list of devices. 
They list in order (with newest devices appearing at the bottom), so this 
method will end up choosing iPhone-6s-plus for now. I'll copy the same function 
in medic-run.js and medic-log.js to ensure they choose the same thing. Is that 
alright with you? It works for CI, but it will fail on a user's machine if they 
manually started another simulator (which shouldn't be a big deal, won't come 
up on buildbot).


> Gathering logs fails in cordova-ios CI
> --------------------------------------
>
>                 Key: CB-10474
>                 URL: https://issues.apache.org/jira/browse/CB-10474
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Medic
>         Environment: OSX
>            Reporter: Richard B Knoll
>            Assignee: Richard B Knoll
>              Labels: found-by-ci, ios, triaged
>
> In the cordova-ios Build Bot CI, the gathering logs step always fails. It 
> tries to {{cat}} a file for the log that does not exist. Here is an example 
> build: 
> https://ci.apache.org/builders/cordova-ios/builds/1607/steps/gathering-logs/logs/stdio



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to