The process '/Users/runner/work/1/s/gradlew' failed with exit code 1 #9924
Comments
|
HI team, this is a urgent issue, we require immediate help on this. |
erik-bershel
added
the
investigate
|
Hey @LeeCeline and @TteamMBK! Unfortunately, it is not possible to investigate the problem using the information provided. Could you provide an example project with the repro steps? It will also be very cool if you can give access to fallen runs.
Our test projects with gradle work, but there is a possibility that your problem is related to |
|
I confirm that there were similar problems before also, but with a lower fail rate. As i can see, we are able to build the project without any error on android studio. For providing access to fallen runs, we are checking internally that we can provide it to you or not due to policies. |
erik-bershel
added
bug
|
Hey @TteamMBK!
Then I can say with confidence that your builds are not compatible with the current runners realisation, unfortunately. I'm going to close this issue as a duplicate of #9194. Unfortunately, we cannot help with this. |
|
Could you please elaborate about "our builds are not compatible with the current runners realisation". So we can understand better and try to approach in a correct way. |
|
Hey @TteamMBK! Please read the description here: https://docs.veertu.com/anka/anka-virtualization-cli/nested-virtualization/#android-emulators. Anka does not support some nested virtualisation features because of some issues with the Apple virtualisation API. It results in poor Android emulator productivity. |
|
I went through the sites you provided, but still i am not getting why we are referring our R&D towards android emulator. FYI, i am asking you because recently pipeline got success once. we are still not understanding that "why is our pipeline getting failed sometimes" We are open to connect with you on teams for better understanding of the issue. As we already mentioned, we need to find out its solution asap. |
|
Hey @TteamMBK! Sure! Let's start from the beginning. At what step exactly does your build fail? Judging by the available information, it crashes during the testing stage. Since I have no other information about the code/config, I make the assumption that your project can also test the application using the Android Emulator. But as of recently, the already rather poor performance of this tool has reached its minimum among macOS runners due to our platform migration. The emulator's startup time exceeds that of almost any automatic tool which results in timeout while running tests. After the migration all the agents affected by https://docs.veertu.com/anka/anka-virtualization-cli/nested-virtualization/#android-emulators At the same time, I cannot guarantee 100% that the problem is in the Android emulator - with the available information I can only guess.
When you can provide more detailed information about the problem including an example-project or appropriate repro-steps, we can return to investigating the issue. Unfortunately, we do not directly support custom builds. |
|
I understood.
|
|
@TteamMBK is it possible to provide failed run logs too? |
|
Here are the failed logs.
|
|
@TteamMBK great, I'll take a look later. Please do not forget about build links also. No matter if private project - I don't need to open it. |
|
could you please let me know, from where i can get Build links ? |
|
For repro steps, we have just pushed the code to the branch from android studio terminal and run the pipeline as usual, as the result, Links for Failure pipeline : Links for Success pipeline : |
|
is there any update on the issue ? |
|
Its been 2 weeks, we are in very urgent situation, this pipeline issue is creating a blockage for our application release and has many bad impact on business. |
|
Hi @TteamMBK Is the issue still ongoing? Could you please attach the latest failure and success logs so that we can analyze them? |
|
Hi @vinaynaikr08, Our project is in very difficult situation right now, we are facing blockage because of the pipeline issue. Please try to provide quick support. |
|
any updates on the tickets. |
|
Hey @TteamMBK! After a dipper investigation of the failed run logs I may say that the issue itself should not be related to the virtualisation platform changes as I thought. There is no sign of resource related issues nether timeouts. From logs I found only some build issue that seems to be project and/or dependencies related. steps:
- task: Gradle@2
inputs:
workingDirectory: ''
gradleWrapperFile: 'gradlew'
options: '$current_options --debug --stacktrace'In general we do not solve this kind of issues, but lets see more informative output just in case we could help. |
erik-bershel
added
Area: Common Tools
and removed
bug
|
Hey @TteamMBK! Feel free to ping me when new logs collected. I'm closing this now as a stale. |
Description
While running the pipeline in azure devops for Android application, there was an issue due to which the pipeline failed -
"The process '/Users/runner/work/1/s/gradlew' failed with exit code 1"
Here is the iscreenshot
What can be done to mitigate the above issue as sometimes when we are running the pipeline, pipeline is successful but sometimes it is getting the error as mentioned above.
Recently it has started failing a lot and success rate is a bit low which is causing problem as it is much more time consuming.
Platforms affected
Runner images affected
Image version and build link
Runner Image
Image: macos-12
Version: 20240514.3
Included Software: https://github.com/actions/runner-images/blob/macOS-12/20240514.3/images/macos/macos-12-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/macOS-12%2F20240514.3
Runner Image Provisioner
2.0.369.1+55cddbb57f254a369b6e7b3b508cebdbee5d24be
Current image version: '20240514.3'
Is it regression?
Yes, but could not provide build link
Expected behavior
Pipeline should be working as expected.
Actual behavior
It was working few days ago, but currently not working as mentioned in description.
Repro steps
Android
Build your Android project with Gradle.
Add steps that test, sign, and distribute the APK, save build artifacts, and more:
https://docs.microsoft.com/azure/devops/pipelines/languages/android
name: '$(prime).$(major).$(minor)'
pool:
vmImage: 'macos-latest'
steps:
task: Bash@3
inputs:
targetType: 'inline'
script: |
#!/usr/bin/env bash
MANIFEST_PATH=app/src/main/AndroidManifest.xml
VERSION_NAME=$(prime).$(major).$(minor)
BUILD_NUMBER=$(Build.BuildId)
TEMP_MANIFEST_PATH=${MANIFEST_PATH}.txt
echo "Version Code=$BUILD_NUMBER"
echo "Version Name=$VERSION_NAME"
cat ${MANIFEST_PATH} | sed "s/android:versionCode="."/android:versionCode="${BUILD_NUMBER}"/" > ${TEMP_MANIFEST_PATH}
cat ${TEMP_MANIFEST_PATH} | sed "s/android:versionName="."/android:versionName="${VERSION_NAME}"/" > ${MANIFEST_PATH}
rm -f ${TEMP_MANIFEST_PATH}
task: Gradle@2
inputs:
workingDirectory: ''
gradleWrapperFile: 'gradlew'
gradleOptions: '-Xmx3072m'
javaHomeOption: 'JDKVersion'
jdkVersionOption: '1.8'
jdkArchitectureOption: 'x64'
publishJUnitResults: false
testResultsFiles: '**/TEST-*.xml'
tasks: assembleINTRelease
task: AndroidSigning@3
inputs:
apkFiles: '**/*.apk'
apksignerKeystoreFile: 'android_keystore'
apksignerKeystorePassword: '$(keystorePassword)'
apksignerKeystoreAlias: '$(keystoreAlias)'
apksignerKeyPassword: '$(keystoreAliasPassword)'
apksignerArguments: '--v1-signing-enabled true --v2-signing-enabled true --verbose'
zipalign: false
task: CopyFiles@2
inputs:
contents: '**/*.apk'
targetFolder: '$(build.artifactStagingDirectory)'
task: PublishBuildArtifacts@1
task: AppCenterDistribute@3
inputs:
serverEndpoint: 'Daimler_Android_AppCenter'
appSlug: 'Daimler-Care4Me-1/Care4Me-Int-1'
appFile: '$(build.artifactStagingDirectory)/**/*.apk'
symbolsOption: 'Android'
releaseNotesOption: 'input'
releaseNotesInput: 'Automated Release'
destinationType: 'groups'
The text was updated successfully, but these errors were encountered: