Started by user Simon Pruvost
Running as SYSTEM
Building in workspace /var/lib/jenkins/jobs/first/workspace
The recommended git tool is: NONE
using credential 8a11502e-f80d-4742-a451-704b40f19292
 > git rev-parse --resolve-git-dir /var/lib/jenkins/jobs/first/workspace/.git # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://framagit.org/pruvosim/store-prices-watchdog.git # timeout=10
Fetching upstream changes from https://framagit.org/pruvosim/store-prices-watchdog.git
 > git --version # timeout=10
 > git --version # 'git version 2.39.5'
using GIT_ASKPASS to set credentials 
 > git fetch --tags --force --progress -- https://framagit.org/pruvosim/store-prices-watchdog.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/dev^{commit} # timeout=10
Checking out Revision ef168bb595d8dcad6a168422ec5f46a94e99de71 (refs/remotes/origin/dev)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ef168bb595d8dcad6a168422ec5f46a94e99de71 # timeout=10
Commit message: "Addind missing file"
 > git rev-list --no-walk ef168bb595d8dcad6a168422ec5f46a94e99de71 # timeout=10
[workspace] $ /bin/sh -xe /tmp/jenkins16283660712413490980.sh
+ python -m venv my-venv
+ my-venv/bin/pip install -r config/requirements.txt
Requirement already satisfied: peewee==3.17.9 in ./my-venv/lib/python3.11/site-packages (from -r config/requirements.txt (line 1)) (3.17.9)
Requirement already satisfied: requests==2.32.3 in ./my-venv/lib/python3.11/site-packages (from -r config/requirements.txt (line 2)) (2.32.3)
Requirement already satisfied: discord-webhook==1.4.1 in ./my-venv/lib/python3.11/site-packages (from -r config/requirements.txt (line 3)) (1.4.1)
Requirement already satisfied: psycopg2==2.9.10 in ./my-venv/lib/python3.11/site-packages (from -r config/requirements.txt (line 4)) (2.9.10)
Requirement already satisfied: playwright==1.51.0 in ./my-venv/lib/python3.11/site-packages (from -r config/requirements.txt (line 5)) (1.51.0)
Requirement already satisfied: charset-normalizer<4,>=2 in ./my-venv/lib/python3.11/site-packages (from requests==2.32.3->-r config/requirements.txt (line 2)) (3.4.1)
Requirement already satisfied: idna<4,>=2.5 in ./my-venv/lib/python3.11/site-packages (from requests==2.32.3->-r config/requirements.txt (line 2)) (3.10)
Requirement already satisfied: urllib3<3,>=1.21.1 in ./my-venv/lib/python3.11/site-packages (from requests==2.32.3->-r config/requirements.txt (line 2)) (2.4.0)
Requirement already satisfied: certifi>=2017.4.17 in ./my-venv/lib/python3.11/site-packages (from requests==2.32.3->-r config/requirements.txt (line 2)) (2025.1.31)
Requirement already satisfied: pyee<13,>=12 in ./my-venv/lib/python3.11/site-packages (from playwright==1.51.0->-r config/requirements.txt (line 5)) (12.1.1)
Requirement already satisfied: greenlet<4.0.0,>=3.1.1 in ./my-venv/lib/python3.11/site-packages (from playwright==1.51.0->-r config/requirements.txt (line 5)) (3.2.0)
Requirement already satisfied: typing-extensions in ./my-venv/lib/python3.11/site-packages (from pyee<13,>=12->playwright==1.51.0->-r config/requirements.txt (line 5)) (4.13.2)
+ pip uninstall playwright
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.
    
    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.
    
    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.
    
    See /usr/share/doc/python3.11/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
Build step 'Execute shell' marked build as failure
Finished: FAILURE