Skip to content

Conversation

@jonpryor
Copy link
Contributor

Context: #8580

Does It Build™?

It should build, it used to build (on 2023-09-02), but #8580 doesn't build, as it's trying to reference
android-toolchain/sdk/build-tools/34.0.0/mainDexClasses.rules, which doesn't exist.

Furthermore, AFAICT xaprepare uses $(XABuildToolsVersion) to specify which build-tools package is installed, which has been 34 since 326ac88, so… how did it build then and why is it failing to build now? What am I missing?

jonpryor and others added 2 commits December 11, 2023 21:38
Context: #8580

Does It Build™?

It *should* build, it *used* to build (on 2023-09-02), but #8580
*doesn't* build, as it's trying to reference
`android-toolchain/sdk/build-tools/34.0.0/mainDexClasses.rules`,
which doesn't exist.

Furthermore, AFAICT `xaprepare` uses `$(XABuildToolsVersion)` to
specify which build-tools package is installed, which has been `34`
since 326ac88, so… how did it build then and why is it failing to
build now?  What am I missing?
Commit d954ff6 likely should have broken the d17-5 build in the same
way that it is currently failing:

"/Users/builder/azdo/_work/4/s/xamarin-android/tests/Mono.Android-Tests/Runtime-MultiDex/Mono.Android-TestsMultiDex.csproj" (default target) (32:6) ->
(_CompileToDalvik target) ->
  MSBUILD : java error JAVA0000: Error in /Users/builder/android-toolchain/sdk/build-tools/34.0.0/mainDexClasses.rules: [/Users/builder/azdo/_work/4/s/xamarin-android/tests/Mono.Android-Tests/Runtime-MultiDex/Mono.Android-TestsMultiDex.csproj]
MSBUILD : java error JAVA0000: Failed to read file: /Users/builder/android-toolchain/sdk/build-tools/34.0.0/mainDexClasses.rules [/Users/builder/azdo/_work/4/s/xamarin-android/tests/Mono.Android-Tests/Runtime-MultiDex/Mono.Android-TestsMultiDex.csproj]
MSBUILD : java error JAVA0000: Compilation failed [/Users/builder/azdo/_work/4/s/xamarin-android/tests/Mono.Android-Tests/Runtime-MultiDex/Mono.Android-TestsMultiDex.csproj]

However, I believe builds including d954ff6 succeeded because the build
machines likely still had build-tools 32.0.0 packages installed.  Our
build pools are re-imaged and refreshed somewhat regularly, and they
seemingly no longer have build-tools 32.0.0 as we do not provision it.

The d17-5 branch does however still provision build tools 30.0.3 for
certain tests, and we can hopefully build our test projects with this
version to avoid the error highlighted above.
@jonpryor jonpryor marked this pull request as ready for review December 18, 2023 23:19
@jonpryor jonpryor merged commit 58bf6ab into d17-5 Dec 18, 2023
@jonpryor jonpryor deleted the dev/jonp/jonp-sanity-check-d17-5 branch December 18, 2023 23:23
@github-actions github-actions bot locked and limited conversation to collaborators Jan 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants