Profiling a Gradle sync mixes up output traces

[jbartok]

A sync process usually triggers multiple Gradle builds. This can be confirmed independently of the Gradle profiler, for example with this process: https://jetbrains.slack.com/docs/T0288D531/F06N56J6CBS

For example, a sync on the gradle/gradle repo triggers 3 Gradle builds.

When profiling the sync with the Gradle profiler and producing chrome traces (--profile chrome-trace), we do get 3 separate result files, like:

• androidStudioSync-8.7-rc-3-measured-build-1-invocation-1-trace.json
• androidStudioSync-8.7-rc-3-measured-build-1-invocation-2-trace.json
• androidStudioSync-8.7-rc-3-measured-build-1-invocation-3-trace.json

However, the content of the files is somehow wrong. All 3 files contain almost the same exact trace, but slightly different. What makes this most suspicious is that the 3 different Gradle build making up the sync process aren't similar (can be confirmed by the above linked JetBrains method).

Not sure exactly what's happening, but the data is very suspicious.