Conversation
|
patrick-stephens
left a comment
There was a problem hiding this comment.
I think you missed updating the workflow that actually builds the containers for the target:
fluent-bit/.github/workflows/call-build-images.yaml
Lines 80 to 92 in 96a88df
It also looks like some Monkey changes which I think need to go via the upstream project @leonardo-albertovich ?
c9b471a to
0350361
Compare
|
@patrick-stephens The (new) custom_calyptia.sh test is crashing after appearing hanged for a few minutes. Is there something I am missing, or do I need to debug it? |
The test is this one I think you mean: https://github.com/fluent/fluent-bit/blob/master/tests/runtime_shell/custom_calyptia.sh It is using YAML config as well so make sure that's enabled but it should be. If |
If I set CALYPTIA_FLEET_TOKEN to a random value the test fails, and if I set it to blank the test hangs and eventually crashes. The test passes on an Intel VM. |
Signed-off-by: Sumit Dubey <sumit.dubey2@ibm.com>
Signed-off-by: Sumit Dubey <sumit.dubey2@ibm.com>
Signed-off-by: Sumit Dubey <sumit.dubey2@ibm.com>
|
@patrick-stephens This is what the test prints on Intel. Is it expected, or is it a bug: |
|
It looks like it is not skipping it for some reason when the variable is not set, or have you set it to the empty value? |
|
[2025/03/25 03:33:01] [ warn] [env] variable ${CALYPTIA_FLEET_TOKEN} is used but not set |
|
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
IBM Power (ppc64le) support. Built locally.
None
Enter
[N/A]in the box, if an item is not applicable to your change.Testing
Before we can approve your change; please submit the following in a comment:
(To be tested on CI)
(To be tested on CI)
If this is a change to packaging of containers or native binaries then please confirm it works for all targets.
(To be tested on CI)
ok-package-testlabel to test for all targets (requires maintainer to do).Documentation
Backporting
Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.