Skip to content

Conversation

@engelmi
Copy link
Member

@engelmi engelmi commented Dec 10, 2025

This is a backport of these commits:

The test cases for too long log configs (level, target and isquiet) causes
the bluechi-agent service to fail (as expected). However, this happens in
the test setup phase where we expect a running agent. Due to timing issues
this check might even pass, depending how fast the status is being checked.
This causes the test to be flacky.
Since such a long input for log configs is unrealistic and the proper level
for testing is on the unit level (test without the long data is already in
place), these cases have een removed.
In addition, the unused BluechiConfig variable for max line length has been
removed.

Signed-off-by: Michael Engel <mengel@redhat.com>
@engelmi engelmi changed the base branch from main to bluechi-1.0.z December 10, 2025 11:47
@engelmi engelmi requested a review from rhatdan as a code owner December 10, 2025 11:47
Since systemd 253, systemctl returns error code 4 when the is-enabled
command is applied to non-existent unit. This differs from bluechictl
is-enabled since here the error code for the sd_bus_call_method is
returned.

Signed-off-by: Michael Engel <mengel@redhat.com>
Signed-off-by: Michael Engel <mengel@redhat.com>
@engelmi engelmi changed the title Backport: Remove test data with too long log configs Backport: Remove test data with too long log configs, const specifier fix and bluechi-is-enabled test fix Dec 10, 2025
Copy link
Member

@mwperina mwperina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@engelmi engelmi merged commit 010c26a into eclipse-bluechi:bluechi-1.0.z Dec 11, 2025
9 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants