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

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

Github user riknoll commented on a diff in the pull request:

    https://github.com/apache/cordova-medic/pull/73#discussion_r51514960
  
    --- Diff: medic/medic-log.js ---
    @@ -69,18 +70,72 @@ function logBlackberry() {
         return;
     }
     
    -function logIOS() {
    -    var logScriptpath = path.join("mobilespec", "platforms", "ios", 
"cordova", "console.log");
    -    var command = "cat " + logScriptpath;
    +function logIOS(appPath) {
    +    // We need to print out the system log for the simulator app. In order 
to figure
    +    // out the path to that file, we need to find the ID of the simulator 
running
    +    // mobilespec
    +
    +    // First, figure out the simulator that ran mobilespec. "cordova run"" 
just chooses
    +    // the last simulator in this list that starts with the word "iPhone"
    +    shelljs.pushd(appPath);
    +
    +    var findSimCommand = getLocalCLI() + " run --list --emulator | grep 
^iPhone | tail -n1";
    --- End diff --
    
    Why would the Windows build machines run this? It's iOS


> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to