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

fix(tests): make run_regression_tests.sh work locally #2020

Merged
merged 1 commit into from
Jun 13, 2022

Conversation

LucaGuerra
Copy link
Contributor

@LucaGuerra LucaGuerra commented May 25, 2022

Signed-off-by: Luca Guerra luca@guerra.sh

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

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

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

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:

The Falco manual and the README in the test directory tell how to run the Falco test suite locally. I think it's very valuable during development however the instructions are a little outdated I believe since:

  1. running the commands as shown would make a few test fail because they cannot find trace files
  2. the instructions ask the user to run a cmake target test-trace-files which has been removed in PR Cmake speedups #1905

It looks like the script assumes to be launched from the trace files directory as all of their paths are relative.

In addition, I don't exactly know why, but it looks like trace files exist both in the Falco repo and in an external storage. Maybe some other contributor or maintainers have more clues about that.

The PR updates the readme file and launches the test from the trace file directory.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

@leogr
Copy link
Member

leogr commented May 26, 2022

/milestone 0.33.0

@poiana poiana added this to the 0.33.0 milestone May 26, 2022
jasondellaluce
jasondellaluce previously approved these changes Jun 6, 2022
Copy link
Contributor

@jasondellaluce jasondellaluce 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 Jun 6, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jasondellaluce, LucaGuerra

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:

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

@poiana
Copy link
Contributor

poiana commented Jun 6, 2022

LGTM label has been added.

Git tree hash: bb52ced9f6d34dbff13ef8cfa4d89f7018ef0b75

@poiana poiana added the approved label Jun 6, 2022
Signed-off-by: Luca Guerra <luca@guerra.sh>
@poiana poiana added the lgtm label Jun 11, 2022
@poiana
Copy link
Contributor

poiana commented Jun 11, 2022

LGTM label has been added.

Git tree hash: d5567b1e9391f7ce4f3fe1342333c07484b3fb04

@poiana poiana merged commit 9d7153e into falcosecurity:master Jun 13, 2022
@LucaGuerra LucaGuerra deleted the fix/run-tests-locally branch June 13, 2022 07:41
@jasondellaluce jasondellaluce removed this from the 0.33.0 milestone Jun 17, 2022
@jasondellaluce jasondellaluce added this to the 0.32.1 milestone Jun 17, 2022
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