fastlane: Timed out trying to set AX messaging timeout

New Issue Checklist

Issue Description

When running scan on travis-ci.org my builds fail with a strange error (see below). This doesn’t happen when running locally (using Xcode 8 Beta 6).

Complete output when running fastlane, including the stack trace and command used

https://travis-ci.org/AlexChesters/schedule-ios/builds/156441330

Testing failed:
Test target scheduleUITests encountered an error (Timed out trying to set AX messaging timeout. If you believe this error represents a bug, please attach the log file at /Users/travis/Library/Developer/Xcode/DerivedData/schedule-bvgggwnybgkfjmbfdxscmrgvxdqf/Logs/Test/6CC6B04E-17A8-48AE-8CD2-3F5017C07E60/Session-scheduleUITests-2016-08-31_073846-ITuN7a.log)
** TEST FAILED **
[07:40:46]: Exit status: 65
[07:40:46]: Variable Dump:
[07:40:46]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios test", :SCAN_DERIVED_DATA_PATH=>"/Users/travis/Library/Developer/Xcode/DerivedData/schedule-bvgggwnybgkfjmbfdxscmrgvxdqf", :SCAN_GENERATED_PLIST_FILES=>["/Users/travis/Library/Developer/Xcode/DerivedData/schedule-bvgggwnybgkfjmbfdxscmrgvxdqf/Logs/Test/6CC6B04E-17A8-48AE-8CD2-3F5017C07E60_TestSummaries.plist"], :SCAN_GENERATED_PLIST_FILE=>"/Users/travis/Library/Developer/Xcode/DerivedData/schedule-bvgggwnybgkfjmbfdxscmrgvxdqf/Logs/Test/6CC6B04E-17A8-48AE-8CD2-3F5017C07E60_TestSummaries.plist"}

Configuration Files

Please copy the complete content of your Fastfile and any other configuration files you use below:

Fastfile:

default_platform :ios

platform :ios do
  before_all do
    fastlane_version "1.102.0"
  end

  desc "Runs all the tests"
  lane :test do
    scan(scheme: 'schedule')
  end
end

Environment

fastlane version (run fastlane -v): 1.102.0 Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? Yes Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? Yes

This is the repo affected by the issue: https://github.com/AlexChesters/schedule-ios

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 17 (2 by maintainers)

Most upvoted comments

@TKBurner Rebooting fixed this for me. No idea why.