Skip to content

[v255] test: fix TEST-84-STORAGETM with nvme-cli < 2.7#484

Merged
bluca merged 1 commit intosystemd:v255-stablefrom
bluca:v255-stable
May 29, 2025
Merged

[v255] test: fix TEST-84-STORAGETM with nvme-cli < 2.7#484
bluca merged 1 commit intosystemd:v255-stablefrom
bluca:v255-stable

Conversation

@bluca
Copy link
Member

@bluca bluca commented May 29, 2025

The -vv parameter was added in version 2.7, check before using it

Follow-up for ebc0514

(cherry picked from commit 60491ce)
(cherry picked from commit f75ca4648efd92e6a7a5a244a5de09187a30e43c)
(cherry picked from commit 4227d16e5623ed085afe5a4773fa81845ffa0179)

The -vv parameter was added in version 2.7, check before using it

Follow-up for ebc0514

(cherry picked from commit 60491ce)
(cherry picked from commit f75ca4648efd92e6a7a5a244a5de09187a30e43c)
(cherry picked from commit 4227d16e5623ed085afe5a4773fa81845ffa0179)
@packit-as-a-service
Copy link

We were not able to find or create Copr project packit/systemd-systemd-stable-484 specified in the config with the following error:

Cannot create a new Copr project (owner=packit project=systemd-systemd-stable-484 chroots=[]): chroots: '[]' is not a valid choice for this field..

Unless the HTTP status code above is >= 500, please check your configuration for:

  1. typos in owner and project name (groups need to be prefixed with @)
  2. whether the project name doesn't contain not allowed characters (only letters, digits, underscores, dashes and dots must be used)
  3. whether the project itself exists (Packit creates projects only in its own namespace)
  4. whether Packit is allowed to build in your Copr project
  5. whether your Copr project/group is not private

@bluca bluca merged commit 866a9a5 into systemd:v255-stable May 29, 2025
22 of 28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments