Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(tests): new e2e tests [4/N] #1763

Merged
merged 1 commit into from
Mar 27, 2024

Conversation

therealbobo
Copy link
Contributor

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area API-version

/area build

/area CI

/area driver-kmod

/area driver-bpf

/area driver-modern-bpf

/area libscap-engine-bpf

/area libscap-engine-gvisor

/area libscap-engine-kmod

/area libscap-engine-modern-bpf

/area libscap-engine-nodriver

/area libscap-engine-noop

/area libscap-engine-source-plugin

/area libscap-engine-savefile

/area libscap

/area libpman

/area libsinsp

/area tests

/area proposals

Does this PR require a change in the driver versions?

/version driver-API-version-major

/version driver-API-version-minor

/version driver-API-version-patch

/version driver-SCHEMA-version-major

/version driver-SCHEMA-version-minor

/version driver-SCHEMA-version-patch

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

Signed-off-by: Roberto Scolaro <roberto.scolaro21@gmail.com>
@FedeDP
Copy link
Contributor

FedeDP commented Mar 26, 2024

/milestone 0.15.0

@poiana
Copy link
Contributor

poiana commented Mar 26, 2024

@FedeDP: The provided milestone is not valid for this repository. Milestones in this repository: [0.16.0, TBD, next-driver]

Use /milestone clear to clear the milestone.

In response to this:

/milestone 0.15.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@FedeDP
Copy link
Contributor

FedeDP commented Mar 26, 2024

/milestone 0.16.0

@poiana poiana added this to the 0.16.0 milestone Mar 26, 2024
uint16_t type = e->get_type();
std::string name(e->get_name());

#if defined(__x86_64__)
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't really like that we are adding per-architecture cases here... since we are supporting more and more architectures in libs i fear these tests will soon become a real mess.

Copy link
Contributor

@FedeDP FedeDP Mar 26, 2024

Choose a reason for hiding this comment

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

I mean: if we have the need to add per-architecture code, it seems we are not actually working at the libsinsp level, since all the arch-dependent code should be tested in drivers IMHO.
cc @Andreagit97

Copy link
Contributor Author

@therealbobo therealbobo Mar 26, 2024

Choose a reason for hiding this comment

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

I don't particularly like my solution but, if we want to stick to the libc wrappers, I think is the only one. Otherwise we can explicitly use the syscall number.

Copy link
Contributor

Choose a reason for hiding this comment

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

I understanrd your point; but i am starting to feel that some of these tests would be better suited for the drivers testing framework :/

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think that this is good point for some of them: in particular the ones where we don't test anything except the syscall (e.g. sys_call_test.stat). For the other ones setting the dropping mode I'm not super sure.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

On the other hand using the libc wrapper on sys_call_test.stat it was instrumental to catch a missing syscall.

Copy link
Contributor

@FedeDP FedeDP left a comment

Choose a reason for hiding this comment

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

/approve

@poiana
Copy link
Contributor

poiana commented Mar 26, 2024

LGTM label has been added.

Git tree hash: ddab90029f875979fda5fa06a37e012e8e1369a7

@poiana
Copy link
Contributor

poiana commented Mar 27, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: FedeDP, jasondellaluce, therealbobo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [FedeDP,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@poiana poiana merged commit df7f57a into falcosecurity:master Mar 27, 2024
43 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants