Closed
Description
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: