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

Required setuptools>=40.0 for running and tests/system/Testbeat.py is not up-to-date in 7.9 #21375

Closed
v1v opened this issue Sep 29, 2020 · 0 comments · Fixed by #21393
Closed
Assignees
Labels
automation bug Team:Automation Label for the Observability productivity team

Comments

@v1v
Copy link
Member

v1v commented Sep 29, 2020

What

  • Required setuptools>=40.0
  • tests/system/Testbeat.py is not up-to-date

Stacktrace

2020-09-29T09:23:56.866Z] ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.
[2020-09-29T09:23:56.866Z] 
[2020-09-29T09:23:56.866Z] We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.
[2020-09-29T09:23:56.866Z] 
[2020-09-29T09:23:56.866Z] pytest-rerunfailures 9.0 requires setuptools>=40.0, but you'll have setuptools 39.0.1 which is incompatible.
[2020-09-29T09:24:09.131Z] Generated fields.yml for testbeat to /var/lib/jenkins/workspace/Beats_beats_PR-21370/src/beatpath/testbeat/fields.yml
[2020-09-29T09:24:14.456Z] =======================
[2020-09-29T09:24:14.456Z] Your custom beat is now available as /var/lib/jenkins/workspace/Beats_beats_PR-21370/src/beatpath/testbeat
[2020-09-29T09:24:14.456Z] =======================
[2020-09-29T09:24:14.456Z] cd /var/lib/jenkins/workspace/Beats_beats_PR-21370/src/beatpath/testbeat ; \
[2020-09-29T09:24:14.456Z] export PATH=${GOPATH}/bin:${PATH}; \
[2020-09-29T09:24:14.456Z] git config user.email "[email protected]" || exit 1 ; \
[2020-09-29T09:24:14.456Z] git config user.name "beats-jenkins" || exit 1 ; \
[2020-09-29T09:24:14.456Z] make check CHECK_HEADERS_DISABLED=y || exit 1 ; \
[2020-09-29T09:24:14.456Z] make || exit 1 ; \
[2020-09-29T09:24:14.456Z] mage test
[2020-09-29T09:24:14.456Z] make[1]: Entering directory '/var/lib/jenkins/workspace/Beats_beats_PR-21370/src/beatpath/testbeat'
[2020-09-29T09:24:17.007Z] >> fmt - autopep8: Formatting Python code
[2020-09-29T09:24:17.007Z] >> fmt - goimports: Formatting Go code
[2020-09-29T09:24:21.322Z] Cache entry deserialization failed, entry ignored
[2020-09-29T09:24:39.462Z] ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.
[2020-09-29T09:24:39.463Z] 
[2020-09-29T09:24:39.463Z] We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.
[2020-09-29T09:24:39.463Z] 
[2020-09-29T09:24:39.463Z] pytest-rerunfailures 9.0 requires setuptools>=40.0, but you'll have setuptools 39.0.1 which is incompatible.
[2020-09-29T09:24:39.463Z] >> check: Checking source code for common problems
[2020-09-29T09:25:47.399Z] Error: some files are not up-to-date. Run 'mage fmt update' then review and commit the changes. Modified: [tests/system/Testbeat.py]
[2020-09-29T09:25:47.399Z] /var/lib/jenkins/workspace/Beats_beats_PR-21370/pkg/mod/github.com/elastic/beats/[email protected]/libbeat/scripts/Makefile:155: recipe for target 'check' failed
[2020-09-29T09:25:47.399Z] make[1]: *** [check] Error 1
[2020-09-29T09:25:47.399Z] make[1]: Leaving directory '/var/lib/jenkins/workspace/Beats_beats_PR-21370/src/beatpath/testbeat'
[2020-09-29T09:25:47.399Z] ../../common/Makefile:13: recipe for target 'test' failed
[2020-09-29T09:25:47.399Z] make: *** [test] Error 1
[2020-09-29T09:25:47.399Z] make: Leaving directory '/var/lib/jenkins/workspace/Beats_beats_PR-21370/src/github.com/elastic/beats/generator/_templates/beat'

How to reproduce it

make -C generator/_templates/beat test test-package

Further details

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Sep 29, 2020
@kuisathaverat kuisathaverat added automation bug Team:Automation Label for the Observability productivity team labels Sep 29, 2020
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Sep 29, 2020
@kuisathaverat kuisathaverat self-assigned this Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation bug Team:Automation Label for the Observability productivity team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants