[jira] [Created] (ZEPPELIN-6194) Intermittent failure in interpreter-test-non-core (11) job of core GitHub Actions workflow

["Gyeongtae Park (Jira)" <ji...@apache.org>]

Gyeongtae Park created ZEPPELIN-6194:
----------------------------------------

             Summary: Intermittent failure in interpreter-test-non-core (11) job of core GitHub Actions workflow
                 Key: ZEPPELIN-6194
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6194
             Project: Zeppelin
          Issue Type: Task
            Reporter: Gyeongtae Park
            Assignee: Gyeongtae Park
             Fix For: 1.0.0, 0.13.0


*Problem Summary:*

The {{interpreter-test-non-core (11)}} job within the {{core}} GitHub Actions workflow occasionally fails during the Conda environment setup phase. These failures are non-deterministic (flaky) and do not correlate with specific code changes, indicating an environment-related root cause.

*Details:*

The failure typically occurs when resolving dependencies using Conda, with the following error observed:
{code:java}
python: /croot/libsolv-suite.../rules.c:261: solver_addrule: Assertion `!p2 && d > 0' failed. {code}
This assertion failure is triggered by Conda's dependency resolver (libsolv) when it encounters unresolved or conflicting constraints.

Previously, the workflow used channel-priority: true, which corresponds to flexible priority mode. This allowed mixing packages from both conda-forge and defaults, potentially leading to dependency conflicts.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)