rabbit-openqa: encode the product version in job name#3238
Draft
g7 wants to merge 2 commits intoopenSUSE:masterfrom
Draft
rabbit-openqa: encode the product version in job name#3238g7 wants to merge 2 commits intoopenSUSE:masterfrom
g7 wants to merge 2 commits intoopenSUSE:masterfrom
Conversation
The bot in the SUSE side crashed recently [0] due to a
name collision:
File "/godata/pipelines/SUSE.openQA/./scripts/gocd/rabbit-openqa.py", line 284, in check_some_projects
project.update_staging_status(staging)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
File "/godata/pipelines/SUSE.openQA/./scripts/gocd/rabbit-openqa.py", line 175, in update_staging_status
raise Exception(f'Names of job #{id} and #{taken_names[name]} collide: {name}')
Exception: Names of job #17092411 and #16972018 collide: Default-qcow-Updates-Staging-install_ltp+sle-micro+Default-qcow-Updates-Staging@aarch64
This is a bit of a niche situation, as the project is in the
SUSE:SLFO:Kernel:1.0 project, where we share the kernel between SLFO 1.0
and 1.1.
This means that the same tests are run against both Micro 6.0 and Micro
6.1, and might thus collide.
[0] https://botmaster.suse.de/go/tab/build/detail/SUSE.openQA/69498/Run/1/Run
Signed-off-by: Eugenio Paolantonio <eugenio.paolantonio@suse.com>
Member
|
Note that this will break all staging projects as the configured
Hm. Maybe it should indeed be configurable per project. The format of the check name could be templated in an OBS prj attribute. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The bot in the SUSE side crashed recently due to a name collision:
This is a bit of a niche situation, as the project is in the SUSE:SLFO:Kernel:1.0 project, where we share the kernel between SLFO 1.0 and 1.1.
This means that the same tests are run against both Micro 6.0 and Micro 6.1, and might thus collide.
Now, setting this as a Draft since I suppose we should discuss whether this should be applied to every project (where the version information is redundant, and might add entropy to already crowded test names), or maybe gate it to an attribute where it can be enabled on the project side, as it might be useful for just a bunch of projects. Suggestions welcome.