Repository navigation
[Feature/CI-CD]: Add core API tests #198
Description
Activity
- addedenhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is needed
on Jul 8, 2026 - addedrustPull requests that update Rust codePull requests that update Rust codeCI/CDci/cd workflowsci/cd workflows
on Jul 8, 2026 - addedv0.1.5Version 0.1.5 issues trackerVersion 0.1.5 issues tracker
on Jul 9, 2026 Hi Lorenzo,
I reviewed #198 together with the current cortexbrain-common feature layout and
would like to contribute a small, hermetic first slice.Proposed scope:
- add a CI cargo-check matrix for meaningful cortexbrain-common feature
combinations; - fix feature-isolation problems surfaced by the matrix, including the
SslEvent Pod implementation currently not gated by monitoring-structs; - add integration contract tests for the public eBPF/userspace event layouts,
protocol conversion and address conversion; - avoid Docker, Kubernetes and privileged eBPF runtime tests in this first PR;
- avoid metadata and service-discovery files currently touched by Fixed container.name null bug when using Docker. Updated metadata enrichment for k8s environments. Added service cache #216.
The PR would reference #198 and #158 without attempting to close either umbrella
issue.Please confirm that this focused scope is aligned with the current direction.
- add a CI cargo-check matrix for meaningful cortexbrain-common feature
Hi @Daniele-Cangi, tests are absolutely welcomed! The first three points are great to implement. I'm finishing the service cache feature in #216 so it would be great not to touch the metadata and service-cache/service-discovery files. Please make sure to send the PR to the 0.1.5 branch. In case you have any question you can ping me here or you can send me an email!
Reacted by DaCperfect I'll start working on it right away!
- added a commit that references this issue
on Sep 2, 2026 - added a commit that references this issue
on Sep 10, 2026 LorenzoTettamanti commented
on Sep 10, 2026 MemberAuthorMore actionsHi @Daniele-Cangi , I've merged PR #216 in case you want to continue working on this issue! Right now I'm pushing the cortexbrain-common@0.1.4 to the crates.io registries
Hey guys picking up with CLI tests. I will submit my PR next week!
18 remaining items
- added 12 commits that reference this issue
on Sep 28, 2026 Hi Lorenzo, following #217 and your invitation to continue on #198, I'm taking a second small test-only slice against 0.1.5: hermetic contract tests for cortexbrain-common OpenTelemetry metric recording using synthetic events and an in-memory reader. I'll keep Docker, Kubernetes, root, loaded eBPF programs, and metadata/service-discovery changes out of scope. I also noticed the record_enter_mem_alloc documentation disagrees with its events_total increment; I'll surface that in the PR rather than silently changing behavior. Please let me know if you prefer a different boundary.
- added a commit that references this issue
on Oct 3, 2026 @Daniele-Cangi everything is working fine! Thanks!
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsIn Progress
Is your feature request related to a problem?
Yes
Problem Description:
The entire projects needs tests to ensure stability and compatibility accross different kernels
Solution:
Add tests in core crates covering: