gradle/gradle · warning

Isolated Projects dangerously-ignore-problems is ENABLED. Is

Error message

Isolated Projects dangerously-ignore-problems is ENABLED.
Isolated Projects violations are being ignored.
Build outputs may be incorrect and the build may crash unexpectedly.
Use this only to evaluate performance.
Do not use this to produce artifacts.
See ${isolatedProjectsDangerouslyIgnoreProblemsDocumentation.url}

What it means

When Isolated Projects runs with problems deliberately ignored (org.gradle.internal.isolated-projects.dangerously-ignore-problems, or --dangerously-isolate-projects), this banner is printed at build start (afterStart). Isolated Projects requires every project to configure in isolation; violations normally fail the build, but in this mode they are only collected, so configurations may be order-dependent, outputs incorrect, and crashes possible. The banner also triggers a report of the ignored problems.

Source

Thrown at platforms/core-configuration/configuration-cache/src/main/kotlin/org/gradle/internal/cc/impl/problems/ConfigurationCacheProblems.kt:504

            SkipStore -> "skipping"
            is Update -> "updating"
        }

    private
    fun ConfigurationCacheStartParameter.requestedTasksOrDefault() =
        requestedTaskNames.takeIf { it.isNotEmpty() }?.joinToString(" ")

    private
    fun outputDirectoryFor(buildDir: File): File =
        startParameter.customReportOutputDirectory?.resolve(cacheKey.toString())
            ?: buildDir.resolve("reports/configuration-cache/$cacheKey")

    private
    inner class PostBuildProblemsHandler : RootBuildLifecycleListener {

        override fun afterStart() {
            if (isIsolatedProjectsDangerouslyIgnoreProblems) {
                logger.warn(isolatedProjectsDangerouslyIgnoreProblemsBanner())
                reportDangerouslyIgnoringProblems()
            }

            if (isWarningMode) {
                reportConfigurationCacheWarnMode()
            }
        }

        override fun beforeComplete(failure: Throwable?) {
            val summary = summarizer.get()

            val fateOfEntryInBuild = fateOfEntryInBuild(summary)
            fateOfEntryInBuild.message?.let { log(it) }
            buildOperationRunner.emitConfigurationCacheEntryOutcomeOperation(fateOfEntryInBuild.outcome, summary.consoleProblemCount)

            if (isIsolatedProjectsDangerouslyIgnoreProblems) {
                logger.warn(isolatedProjectsDangerouslyIgnoreProblemsBanner())
            }

View on GitHub (pinned to 534f27719b)

Solutions

1. Treat the banner as a stop sign: work through the reported isolated-projects violations until the build passes without the flag
2. Remove org.gradle.internal.isolated-projects.dangerously-ignore-problems from gradle.properties and CI command lines once evaluation is done
3. Never publish or deploy artifacts from builds run in this mode — outputs may be silently incorrect
4. Use the problems report generated alongside the banner as the migration backlog

Example fix

# before
org.gradle.internal.isolated-projects.dangerously-ignore-problems=true

# after (build passes honestly without it)
# org.gradle.internal.isolated-projects.dangerously-ignore-problems=true

# CI gate: never start a shipping build in dangerously-ignore mode
! grep -Rn 'dangerously-ignore-problems' gradle.properties ~/.gradle/gradle.properties 2>/dev/null \
  || { echo "isolated-projects violations are ignored — refusing to build"; exit 1; }

When it happens

Trigger: Running gradle --dangerously-isolate-projects or setting org.gradle.internal.isolated-projects.dangerously-ignore-problems=true in gradle.properties, typically while evaluating isolated-projects performance or while migrating a build that still has cross-project coupling.

Common situations: Benchmarking configuration-cache/isolated-projects gains; migration periods where the flag is used to 'keep builds running'; the flag left enabled globally in CI after migration finished.

Related errors

• Cannot add '%s' to '%s' as it is a filtered collection
• Cannot open package '%s' in module '%s' defined in layer '%s
• Don't know how to serialize objects of type %s.
• Unexpected type tag %d found.
• Don't know how to serialize an object of type %s.

AI-assisted analysis of gradle/gradle@534f27719b (2026-08-22). Data as JSON: /api/errors/a039009413f900cf. Report an issue: GitHub.