Skip to content

install should not do full lock resolution, as that is the purpose of pipenv lock #3559

install should not do full lock resolution, as that is the purpose of pipenv lock

install should not do full lock resolution, as that is the purpose of pipenv lock #3559

Triggered via pull request October 18, 2024 23:42
@matteiusmatteius
synchronize #6276
issue-6267
Status Cancelled
Total duration 14m 35s
Artifacts

ci.yaml

on: pull_request
Check code linting
42s
Check code linting
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

24 errors
Windows / 3.9
Process completed with exit code 1.
MacOS / 3.11
Process completed with exit code 1.
MacOS / 3.10
Process completed with exit code 1.
Ubuntu / 3.11
Process completed with exit code 1.
MacOS / 3.13
Process completed with exit code 1.
MacOS / 3.9
Process completed with exit code 1.
MacOS / 3.8
[notice] A new release of pip is available: 21.1.1 -> 24.2 [notice] To update, run: python3.8 -m pip install --upgrade pip
MacOS / 3.8
Process completed with exit code 1.
Ubuntu / 3.8
Process completed with exit code 1.
MacOS / 3.12
Process completed with exit code 1.
Ubuntu / 3.9
Process completed with exit code 1.
Ubuntu / 3.10
Process completed with exit code 1.
Ubuntu / 3.12
Process completed with exit code 1.
Ubuntu / 3.13
Process completed with exit code 1.
Windows / 3.13
Canceling since a higher priority waiting request for 'CI- branch- 6276' exists
Windows / 3.13
The operation was canceled.
Windows / 3.12
Canceling since a higher priority waiting request for 'CI- branch- 6276' exists
Windows / 3.12
The operation was canceled.
Windows / 3.10
Canceling since a higher priority waiting request for 'CI- branch- 6276' exists
Windows / 3.10
The operation was canceled.
Windows / 3.11
Canceling since a higher priority waiting request for 'CI- branch- 6276' exists
Windows / 3.11
The operation was canceled.
Windows / 3.8
Canceling since a higher priority waiting request for 'CI- branch- 6276' exists
Windows / 3.8
The operation was canceled.