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

[CI] Upload test result files #17907

Closed
kuisathaverat opened this issue Apr 22, 2020 · 3 comments · Fixed by #18695
Closed

[CI] Upload test result files #17907

kuisathaverat opened this issue Apr 22, 2020 · 3 comments · Fixed by #18695
Assignees
Labels
automation ci Team:Automation Label for the Observability productivity team

Comments

@kuisathaverat
Copy link
Contributor

kuisathaverat commented Apr 22, 2020

The test suit generates some files (build/system-tests) that are needed for diagnosing issues, we have to upload those files to Jenkins to help to diagnose when an error happens.

see https://github.com/elastic/apm-server/blob/master/Jenkinsfile#L303-L305

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 27, 2020
@andresrc andresrc removed the needs_team Indicates that the issue/PR needs a Team:* label label Apr 28, 2020
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 28, 2020
@andresrc andresrc removed the needs_team Indicates that the issue/PR needs a Team:* label label Apr 28, 2020
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 28, 2020
@andresrc andresrc removed the needs_team Indicates that the issue/PR needs a Team:* label label Apr 28, 2020
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 28, 2020
@andresrc andresrc added the Team:Automation Label for the Observability productivity team label May 13, 2020
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label May 13, 2020
@v1v
Copy link
Member

v1v commented May 29, 2020

This is tricky one :P

I've seen those system-tests folder contains symlinks, if the idea is to archive them as a tarball then no issues, otherwise, the implementation #18695 might be something to look at, there is a specific CI archiving implementation to bypass some issues when archiving files in big repositories. The system-tests\ folder has been skipped to bypass some issues with symlinks:

[2020-05-28T17:29:16.586Z] FileExistsError: [WinError 183] Cannot create a file when that file already exists: '\\\\?\\C:\\Users\\jenkins\\workspace\\Beats_beats-beats-mbp_PR-18695\\src\\github.com\\elastic\\beats\\auditbeat\\build\\system-tests\\run\\test_file_integrity.Test.test_non_recursive' -> 'build\\.\\build\\auditbeat\\build\\system-tests\\last_run'

@kuisathaverat
Copy link
Contributor Author

there are tons of files, on the APM Server we upload a tar file with all the content of the folder.

@v1v
Copy link
Member

v1v commented Jul 20, 2020

For the record, test result files for the integration tests are now uploaded to the build as artifacts:

image

Format: <beat-name>--system-tests-<os>.tgz

For instance:

  • libbeat--system-tests-linux.tgz
  • metricbeat--system-tests-darwin.tgz
  • metricbeat--system-tests-linux.tgz

@zube zube bot removed the [zube]: Done label Oct 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation ci Team:Automation Label for the Observability productivity team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants