Project

General

Profile

Actions

Bug #22751

open

Build fails if higher-level Python tools get a later version than their dependencies

Added by Brett Smith 2 days ago. Updated 2 days ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Deployment
Target version:
-
Story points:
-

Description

Steps to reproduce:

  1. In a -staging branch, make a commit to a high-level tool that uses the Python SDK like tools/cluster-activity, without making any commits to sdk/python etc.
  2. Run the test suite.

Expected result: tests pass.

Actual result: the install fails with an error like this:

======= install tools/cluster-activity
Using /tmp/workspace/developer-run-tests-doc-sdk-java-R/tools/cluster-activity for version number calculation of /tmp/workspace/developer-run-tests-doc-sdk-java-R/tools/cluster-activity
Processing /tmp/workspace/developer-run-tests-doc-sdk-java-R/tools/cluster-activity
ERROR: Could not find a version that satisfies the requirement arvados-python-client~=3.1.1.dev0 (from arvados-cluster-activity)
ERROR: No matching distribution found for arvados-python-client~=3.1.1.dev0
======= tools/cluster-activity install -- FAILED

The reason this fails is because the SDK only got built with version 3.1.0 because it has no more recent commits that would make it eligible to be 3.1.1:

Successfully installed arvados-python-client-3.1.0.dev20250314161126
======= install sdk/python -- 2s

So either we need to set a better floor for generated version numbers, or relax the dependency between Python modules.


Files


Related issues 1 (1 open0 closed)

Related to Arvados - Support #22370: Rework how development and testing/release package versions are determined in the source treeNewBrett SmithActions
Actions

Also available in: Atom PDF