ParkGyeongTae opened a new pull request, #4937:
URL: https://github.com/apache/zeppelin/pull/4937
### What is this PR for?
**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:
```bash
python: /croot/libsolv-suite.../rules.c:261: solver_addrule: Assertion `!p2
&& d > 0' failed.
```
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.
**Resolution:**
The Conda configuration has been updated to use channel-priority: strict,
ensuring that all dependencies are resolved from conda-forge unless unavailable:
```bash
with:
...
channel-priority: strict
...
```
After this change, the flaky behavior during environment setup was no longer
observed in repeated runs.
### What type of PR is it?
Bug Fix
### Todos
* [x] - Update `setup-miniconda` configuration
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN/ZEPPELIN-6194
### How should this be tested?
* This should be validated by re-running the `core` workflow multiple times
to confirm that the flaky behavior in `interpreter-test-non-core (11)` no
longer occurs during Conda environment setup.
### Screenshots (if appropriate)
N/A
### Questions:
* Does the license files need to update? No.
* Is there breaking changes for older versions? No.
* Does this needs documentation? No.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscr...@zeppelin.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
