Closed pre-commit-ci[bot] closed 4 weeks ago
@wolfv do you understand the failure here?
I looked at the solver differences between mamba and rattler. The two entries look like this:
{
"key": "vc-14.3-h8a93ad2_22.conda",
"value": {
"build": "h8a93ad2_22",
"build_number": 22,
"depends": [
"vc14_runtime >=14.40.33810"
],
"license": "BSD-3-Clause",
"license_family": "BSD",
"md5": "a47cd756e88d8a80dfae678842d4acc9",
"name": "vc",
"sha256": "b72e7410ec0a748d21e9e997234fc474e3367cee8f509b07eb8182d3584a38d8",
"size": 17462,
"subdir": "win-64",
"timestamp": 1728400826503,
"track_features": "vc14",
"version": "14.3"
}
}
{
"key": "vc-14.3-ha32ba9b_22.conda",
"value": {
"build": "ha32ba9b_22",
"build_number": 22,
"depends": [
"vc14_runtime >=14.38.33135"
],
"license": "BSD-3-Clause",
"license_family": "BSD",
"md5": "311c9ba1dfdd2895a8cb08346ff26259",
"name": "vc",
"sha256": "2a47c5bd8bec045959afada7063feacd074ad66b170c1ea92dd139b389fcf8fd",
"size": 17447,
"subdir": "win-64",
"timestamp": 1728400826998,
"track_features": "vc14",
"version": "14.3"
}
}
They are very similar, only difference is the lower bound on the dependency.
Rattler selects the one that has the higher timestamp (was built later). I think that's the correct behavior. I am not sure why mamba selects the other one yet.
OK, the problme on the mamba side looks like it's related to dividing the timestamp by 1000:
info libsolv Fallback to timestamp comparison: 1728400826 vs 1728400826: [-1]
info libsolv Selecting variant [a] of (a) vc-14.3-h8a93ad2_22 vs (b) vc-14.3-ha32ba9b_22 (score: -1)
libsolv sees the two timestamps as equal and thus selects a different solution here.
Opened issue in mamba here: https://github.com/mamba-org/mamba/issues/3523
updates: