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

[Auditbeat] Integrations tests get stalled #18977

Closed
v1v opened this issue Jun 4, 2020 · 3 comments
Closed

[Auditbeat] Integrations tests get stalled #18977

v1v opened this issue Jun 4, 2020 · 3 comments
Labels
Auditbeat flaky-test Unstable or unreliable test cases. Stalled

Comments

@v1v
Copy link
Member

v1v commented Jun 4, 2020

I've found some unexpected behaviour as stated in #18777 (comment)

The changes I did in the #18777 are nothing but adding the MODULE env variable if the PR contains any changes related to those specific regex. So far the above PR is doing nothing but running all the stages.

What's the error?

18:49:50  + mage update build test
18:50:17  Generated fields.yml for auditbeat to /var/lib/jenkins/workspace/Beats_beats-beats-mbp_PR-18777/src/github.com/elastic/beats/x-pack/auditbeat/fields.yml
18:50:17  >> Building auditbeat.yml for linux/amd64
...
18:59:55    Failed building wheel for ordered-set
20:28:26  ........Sending interrupt signal to process
20:28:31  Sending interrupt signal to process
20:28:42  Error: running "docker-compose -p auditbeat_8_0_0_f293d87ebe-snapshot run -e DOCKER_COMPOSE_PROJECT_NAME=auditbeat_8_0_0_f293d87ebe-snapshot -e BEAT_STRICT_PERMS=false -e STACK_ENVIRONMENT=snapshot -e TESTING_ENVIRONMENT=snapshot -e GOCACHE=/go/src/github.com/elastic/beats/build/docker-gocache -e EXEC_UID=1156 -e EXEC_GID=1157 -e GOFLAGS=-mod=vendor -e BEATS_INSIDE_INTEGRATION_TEST_ENV=true -e TEST_COVERAGE=true -e RACE_DETECTOR=true -e TEST_TAGS=null,oracle beat /go/src/github.com/elastic/beats/x-pack/auditbeat/build/mage-linux-amd64 pythonIntegTest" failed with exit code 143
20:28:42  script returned exit code 143

What's the potential commit related with the above issue?

As far as I see, #18887 did work as expected for that particular
mage update build test in the auditbeat but it got stalled in the master branch when merging it:

image

@v1v v1v added the Auditbeat label Jun 4, 2020
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 4, 2020
@v1v v1v added the Team:SIEM label Jun 4, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jun 4, 2020
@v1v
Copy link
Member Author

v1v commented Jun 4, 2020

I was not able to reproduce it locally though...

what did I run locally?

$ cd x-pack/auditbeat
$ mage update build test                    
Generated fields.yml for auditbeat to /Users/vmartinez/work/src/github.com/elastic/beats/x-pack/auditbeat/fields.yml

----------------------------------------------------------------------
Ran 18 tests in 786.273s

FAILED (failures=13)
>> python test: Integration Testing Complete
Error: running "/tmp/python-env/build/ve/docker/bin/nosetests --process-timeout=90 --with-timer --with-xunit --xunit-file=build/TEST-python-integration.xml tests/system/test_metricsets.py tests/system/test_system_socket.py" failed with exit code 1
Error: running "docker-compose -p auditbeat_8_0_0_0ee7025fd2-snapshot run -e DOCKER_COMPOSE_PROJECT_NAME=auditbeat_8_0_0_0ee7025fd2-snapshot -e BEAT_STRICT_PERMS=false -e STACK_ENVIRONMENT=snapshot -e TESTING_ENVIRONMENT=snapshot -e GOCACHE=/go/src/github.com/elastic/beats/build/docker-gocache -e EXEC_UID=501 -e EXEC_GID=20 -e BEATS_INSIDE_INTEGRATION_TEST_ENV=true -e GOFLAGS=-mod=vendor beat /go/src/github.com/elastic/beats/x-pack/auditbeat/build/mage-linux-amd64 pythonIntegTest" failed with exit code 1

Further details

It just worked in the master branch , see here

@jsoriano jsoriano added the flaky-test Unstable or unreliable test cases. label Jun 5, 2020
@botelastic
Copy link

botelastic bot commented May 6, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added the Stalled label May 6, 2021
@botelastic botelastic bot closed this as completed Jun 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auditbeat flaky-test Unstable or unreliable test cases. Stalled
Projects
None yet
Development

No branches or pull requests

3 participants