2017/02/13 14:26:50 No base Cache Info found for compare
2017/02/13 14:26:50 New cache will be created âŠ
2017/02/13 14:26:50 => Calculating Fingerprint âŠ
2017/02/13 14:26:50 ==> Fingerprint method: file-content-hash
2017/02/13 14:26:50 (i) No fingerprint generated for path: (/var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/cache001714291) - no file found to generate one
2017/02/13 14:26:50 [!] Failed to calculate fingerprint: Failed to generate fingerprint for paths - no file found to generate one
exit status 1
WARN[14:26:50] Step (cache-push@0.9.4) failed, but was marked as skippable
| |
±â±--------------------------------------------------------------±---------+
| ! | cache-push@0.9.4 (exit code: 1) | 6.54 sec |
±â±--------------------------------------------------------------±---------+
| Issue tracker: https://github.com/bitrise-steplib/steps-cache-push/issues |
| Source: https://github.com/bitrise-steplib/steps-cache-push.git |
±â±--------------------------------------------------------------±---------+
It seems the fingerprint generation failed because there was no file to calculate a fingerprint for. From the log:
...
2017/02/13 14:26:50 (!) Skipping (./Gousto/Carthage/Cachefile): Specified path does not exist
...
2017/02/13 14:26:50 (i) No fingerprint generated for path: (/var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/cache001714291) - no file found to generate one
...
2017/02/13 14:26:50 [!] Failed to calculate fingerprint: Failed to generate fingerprint for paths - no file found to generate one
In case thereâs absolutely no file to cache, the step will fail - but because a missing cache is not an error, itâs just marked as a warning (âStep (cache-push@0.9.4) failed, but was marked as skippableâ).
Based on the log, Iâd say you wanted to cache Carthage dependencies, but it seems the path to the Carthage/Cachefile is not the right one.
Do you use our Carthage step to install the carthage dependencies? That should generate this Cachefile, carthage itself does not (and carthage in itself doesnât really support any caching, or at least that was the case back when we created our step, and the built in cache handling mechanism in the Carthage step).
If you have any questions, just let us know! If you canât figure out why that file is missing, although it should not, please contact us through the onsite chat support or through email, and include the buildâs bitrise.io URL so that we can look into that!
Yes I am using your Carthage build step. All I need is to make it work like before, i really did not change much, all i did was migrate to swift 3.0, then manually cleared the cache, I have not touched the folder locations, I would expect this step to cache the files inside this directory ./Gousto/Carthage as it was before, Question is ./Gousto/Carthage/Cachefile is this the cache destination folder ? i am really not sure
±-----------------------------------------------------------------------------+
| (4) carthage@2.4.0 |
±-----------------------------------------------------------------------------+
| id: carthage |
| version: 2.4.0 |
| collection: https://github.com/bitrise-io/bitrise-steplib.git |
| toolkit: bash |
| time: 2017-02-13T13:50:23-08:00 |
±-----------------------------------------------------------------------------+
| |
INFO[13:50:23] * [OK] Step dependency (carthage) installed, available.
*** Cloning SwiftyUserDefaults
*** Cloning Bolts-Swift
*** Cloning SwiftDate
*** Cloning Alamofire
*** Cloning fmdb
*** Cloning aws-sdk-ios
*** Cloning Kingfisher
*** Cloning DeviceKit
*** Cloning Cartography
*** Cloning XCGLogger
*** Skipped downloading Alamofire.framework binary due to the error:
âAPI rate limit exceeded for 208.52.166.156. (But hereâs the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)â
*** Checking out Alamofire at â4.3.0â
*** Skipped downloading aws-sdk-ios.framework binary due to the error:
âAPI rate limit exceeded for 208.52.166.156. (But hereâs the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)â
*** Checking out aws-sdk-ios at â2.5.0â
*** Skipped downloading Bolts-Swift.framework binary due to the error:
âAPI rate limit exceeded for 208.52.166.156. (But hereâs the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)â
*** Checking out Bolts-Swift at â1.3.0â
*** Skipped downloading Cartography.framework binary due to the error:
âAPI rate limit exceeded for 208.52.166.156. (But hereâs the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)â
*** Checking out Cartography at â1.0.1â
*** Skipped downloading DeviceKit.framework binary due to the error:
âAPI rate limit exceeded for 208.52.166.156. (But hereâs the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)â
*** Checking out DeviceKit at â1.0.1â
*** Skipped downloading fmdb.framework binary due to the error:
âAPI rate limit exceeded for 208.52.166.156. (But hereâs the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)â
*** Checking out fmdb at â2.6.2â
*** Skipped downloading Kingfisher.framework binary due to the error:
âAPI rate limit exceeded for 208.52.166.156. (But hereâs the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)â
*** Checking out Kingfisher at â3.4.0â
*** Skipped downloading SwiftDate.framework binary due to the error:
âAPI rate limit exceeded for 208.52.166.156. (But hereâs the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)â
*** Checking out SwiftDate at â4.0.13â
*** Skipped downloading SwiftyUserDefaults.framework binary due to the error:
âAPI rate limit exceeded for 208.52.166.156. (But hereâs the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)â
*** Checking out SwiftyUserDefaults at â3.0.1â
*** Skipped downloading XCGLogger.framework binary due to the error:
âAPI rate limit exceeded for 208.52.166.156. (But hereâs the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)â
*** Checking out XCGLogger at âVersion_4.0.0â
*** xcodebuild output can be found in /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.4AJpsx.log
*** Building scheme âAlamofire iOSâ in Alamofire.xcworkspace
*** Building scheme âAWSDynamoDBâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSLambdaâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSAPIGatewayâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSRekognitionâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSSimpleDBâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSKinesisâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSEC2â in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSCognitoâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSSESâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSCloudWatchâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSSNSâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSCoreâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSAutoScalingâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSElasticLoadBalancingâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSMachineLearningâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSLexâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSCognitoIdentityProviderâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSMobileAnalyticsâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSPinpointâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSIoTâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSSQSâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSS3â in AWSiOSSDKv2.xcodeproj
*** Building scheme âAWSPollyâ in AWSiOSSDKv2.xcodeproj
*** Building scheme âBoltsSwift-iOSâ in BoltsSwift.xcworkspace
*** Building scheme âCartography-iOSâ in Cartography.xcworkspace
*** Building scheme âDeviceKitâ in DeviceKit.xcodeproj
*** Building scheme âFMDB iOSâ in fmdb.xcodeproj
*** Building scheme âKingfisherâ in Kingfisher.xcworkspace
*** Building scheme âSwiftDate_iOSâ in SwiftDate.xcodeproj
*** Building scheme âSwiftyUserDefaultsâ in SwiftyUserDefaults.xcodeproj
*** Building scheme âXCGLogger (iOS)â in XCGLogger.xcodeproj
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSCognito/AWSCognitoDataset.m:356:102: warning: implicit conversion loses integer precision: âlong longâ to âlongâ [-Wshorten-64-to-32]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSCognito/AWSCognitoDataset.m:356:102: warning: implicit conversion loses integer precision: âlong longâ to âlongâ [-Wshorten-64-to-32]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSCognitoIdentityProvider/Internal/AWSCognitoIdentityProviderSrpHelper.m:213:5: warning: ignoring return value of function declared with warn_unused_result attribute [-Wunused-result]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSCognitoIdentityProvider/Internal/AWSCognitoIdentityProviderSrpHelper.m:213:5: warning: ignoring return value of function declared with warn_unused_result attribute [-Wunused-result]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSCognitoIdentityProvider/Internal/AWSCognitoIdentityProviderSrpHelper.m:213:5: warning: ignoring return value of function declared with warn_unused_result attribute [-Wunused-result]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSCognitoIdentityProvider/Internal/AWSCognitoIdentityProviderSrpHelper.m:213:5: warning: ignoring return value of function declared with warn_unused_result attribute [-Wunused-result]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSIoT/Internal/SocketRocket/AWSSRWebSocket.m:506:5: warning: ignoring return value of function declared with warn_unused_result attribute [-Wunused-result]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSIoT/Internal/SocketRocket/AWSSRWebSocket.m:630:13: warning: enumeration value âNSURLNetworkServiceTypeCallSignalingâ not handled in switch [-Wswitch]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSIoT/Internal/SocketRocket/AWSSRWebSocket.m:1444:9: warning: ignoring return value of function declared with warn_unused_result attribute [-Wunused-result]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSIoT/Internal/SocketRocket/AWSSRWebSocket.m:506:5: warning: ignoring return value of function declared with warn_unused_result attribute [-Wunused-result]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSIoT/Internal/SocketRocket/AWSSRWebSocket.m:630:13: warning: enumeration value âNSURLNetworkServiceTypeCallSignalingâ not handled in switch [-Wswitch]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSIoT/Internal/SocketRocket/AWSSRWebSocket.m:1444:9: warning: ignoring return value of function declared with warn_unused_result attribute [-Wunused-result]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSIoT/Internal/SocketRocket/AWSSRWebSocket.m:506:5: warning: ignoring return value of function declared with warn_unused_result attribute [-Wunused-result]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSIoT/Internal/SocketRocket/AWSSRWebSocket.m:630:13: warning: enumeration value âNSURLNetworkServiceTypeCallSignalingâ not handled in switch [-Wswitch]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSIoT/Internal/SocketRocket/AWSSRWebSocket.m:1444:9: warning: ignoring return value of function declared with warn_unused_result attribute [-Wunused-result]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSIoT/Internal/SocketRocket/AWSSRWebSocket.m:506:5: warning: ignoring return value of function declared with warn_unused_result attribute [-Wunused-result]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSIoT/Internal/SocketRocket/AWSSRWebSocket.m:630:13: warning: enumeration value âNSURLNetworkServiceTypeCallSignalingâ not handled in switch [-Wswitch]
/Users/vagrant/git/Gousto/Carthage/Checkouts/aws-sdk-ios/AWSIoT/Internal/SocketRocket/AWSSRWebSocket.m:1444:9: warning: ignoring return value of function declared with warn_unused_result attribute [-Wunused-result]
Running carthage command: -c carthage update --platform iOS --platform iOS
| |
±â±--------------------------------------------------------------±---------+
| â | carthage@2.4.0 | 36.4 min |
±â±--------------------------------------------------------------±---------+
| Update available: 2.4.0 -> 3.0.5 |
±â±--------------------------------------------------------------±---------+
2017/02/13 14:26:50 No base Cache Info found for compare
2017/02/13 14:26:50 New cache will be created âŠ
2017/02/13 14:26:50 => Calculating Fingerprint âŠ
2017/02/13 14:26:50 ==> Fingerprint method: file-content-hash
2017/02/13 14:26:50 (i) No fingerprint generated for path: (/var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/cache001714291) - no file found to generate one
2017/02/13 14:26:50 [!] Failed to calculate fingerprint: Failed to generate fingerprint for paths - no file found to generate one
exit status 1
WARN[14:26:50] Step (cache-push@0.9.4) failed, but was marked as skippable
| |
±â±--------------------------------------------------------------±---------+
| ! | cache-push@0.9.4 (exit code: 1) | 6.54 sec |
±â±--------------------------------------------------------------±---------+
| Issue tracker: https://github.com/bitrise-steplib/steps-cache-push/issues |
| Source: https://github.com/bitrise-steplib/steps-cache-push.git |
±â±--------------------------------------------------------------±---------+
It seems you use the âupdateâ carthage command (Carthage command to run input of the Carthage step). Can you please try to switch to âbootstrapâ?
The 2.4.0 version of the step I believe only supported cache for âbootstrapâ, but in any case âbootstrapâ should work; update is designed to update every dependency every time (AFAIK).
In the meantime I checked the Carthage docs, and I think the step is right to only generate Cache infos for bootstrap and not for update, as update disregards any dependencies found locally and updates all dependencies every time you run it, so caching it would not help.