Project

General

Profile

Actions
Copy link

action #110262

closed

openqa_review: Github action failed with "tox4: command not found"

Added by jbaier_cz over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
jbaier_cz
Target version:
openQA Project (public) - Ready
Start date:
2022-04-25
Due date:
% Done:

0%

Estimated time:

Description

Seen on https://github.com/os-autoinst/openqa_review/actions/runs/2041575981

The tox invocation started to fail on every Python version but 3.6 with a message tox4: command not found; replacing tox4 with tox will do the opposite and succeeds on every Python version but 3.6 where it fails with tox: command not found. Likely, this is caused by a dependency change as the new (failing) jobs includes tox-3.25.0, the previous (non-failing) used tox-3.24.5.

AC1: The pipeline succeeds on every defined Python version

Actions
Copy link
 #1

Updated by jbaier_cz over 2 years ago

Also: why the hell is the binary named tox4, if the version is 3.x? Unfortunately, using version tox-4.0.0b2 will not make any difference.

Actions
Copy link
 #3

Updated by jbaier_cz over 2 years ago

  • Status changed from New to In Progress
  • Assignee set to jbaier_cz
Actions
Copy link
 #4

Updated by jbaier_cz over 2 years ago

  • Status changed from In Progress to Feedback

It seems, that the problem was caused infact by the tox-gh (and how the support for tox v4 was handled). This should be solved by making a transition to tox-gh-actions as suggested in https://github.com/os-autoinst/openqa_review/pull/213

Actions
Copy link
 #5

Updated by jbaier_cz over 2 years ago

  • Status changed from Feedback to Resolved

Pipeline looks good, no issues reported.

Actions
Copy link

Also available in: Atom PDF