Closed v1v closed 1 year ago
the below badges are clickable and redirect to their specific view in the CI or DOCS
#### Build stats * Build Cause: `Pull request #200 updated` * Start Time: 2021-06-18T13:55:04.284+0000 * Duration: 18 min 28 sec * Commit: a31766a5d8957a1ef188a955753586cf13f6665b #### Test stats :test_tube: | Test | Results | | ------------ | :-----------------------------: | | Failed | 12 | | Passed | 2829 | | Skipped | 1932 | | Total | 4773 | #### Trends :test_tube: ![Image of Build Times](https://beats-ci.elastic.co/job/Beats/job/beats-tester-mbp/job/PR-200/buildTimeGraph/png) ![Image of Tests](https://beats-ci.elastic.co/job/Beats/job/beats-tester-mbp/job/PR-200/7/testReport/history/countGraph/png?start=0&end=25)
> Show only the first 10 test failures ##### `Test Hosts / Matrix - GROUPS = 'windows' / Test / [tester-win12-64] Packaging windows x86 tests for APM Server: test-beat : Save output to host dest=logs/{{ beat_name }}{{ beat_pkg_suffix }}-{{ win_arch | default(ansible_architecture) }}-{{ inventory_hostname }}/output.json, src={{ beat_output_file }}, flat=True – /var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-beat/tasks/main.yml:51`
``` Path c:\ProgramData\apm-server\logs\output.json is not found ```
``` { "changed": false, "msg": "Path c:\\ProgramData\\apm-server\\logs\\output.json is not found" } ```
``` Service 'apm-server (apm-server)' cannot be started due to the following error: Cannot start service apm-server on computer '.'. ```
``` { "can_pause_and_continue": false, "changed": false, "depended_by": [], "dependencies": [], "description": "", "desktop_interact": false, "display_name": "apm-server", "exists": true, "msg": "Service 'apm-server (apm-server)' cannot be started due to the following error: Cannot start service apm-server on computer '.'.", "name": "apm-server", "path": "\"C:\\Users\\Administrator\\apm-server-8.0.0-SNAPSHOT-windows-x86\\apm-server.exe\" --environment=windows_service -c \"C:\\Users\\Administrator\\apm-server-8.0.0-SNAPSHOT-windows-x86\\apm-server.yml\" --path.home \"C:\\Users\\Administrator\\apm-server-8.0.0-SNAPSHOT-windows-x86\" --path.data \"C:\\ProgramData\\apm-server\" --path.logs \"C:\\ProgramData\\apm-server\\logs\" -E logging.files.redirect_stderr=true", "start_mode": "delayed", "state": "stopped", "username": "LocalSystem" } ```
``` the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded The error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - name: Setting heartbeat_file ^ here ```
``` { "msg": "the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded\n\nThe error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Setting heartbeat_file\n ^ here\n" } ```
``` the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded The error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - name: Setting heartbeat_file ^ here ```
``` { "msg": "the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded\n\nThe error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Setting heartbeat_file\n ^ here\n" } ```
``` the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded The error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - name: Setting heartbeat_file ^ here ```
``` { "msg": "the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded\n\nThe error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Setting heartbeat_file\n ^ here\n" } ```
``` the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded The error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - name: Setting heartbeat_file ^ here ```
``` { "msg": "the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded\n\nThe error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Setting heartbeat_file\n ^ here\n" } ```
``` the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded The error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - name: Setting heartbeat_file ^ here ```
``` { "msg": "the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded\n\nThe error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Setting heartbeat_file\n ^ here\n" } ```
``` the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded The error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - name: Setting heartbeat_file ^ here ```
``` { "msg": "the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded\n\nThe error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Setting heartbeat_file\n ^ here\n" } ```
``` the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded The error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - name: Setting heartbeat_file ^ here ```
``` { "msg": "the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded\n\nThe error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Setting heartbeat_file\n ^ here\n" } ```
``` the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded The error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - name: Setting heartbeat_file ^ here ```
``` { "msg": "the field 'args' has an invalid value ({u'heartbeat_file': u'{{ heartbeat_file_record.stdout | from_json }}'}), and could not be converted to an dict.The error was: No JSON object could be decoded\n\nThe error appears to be in '/var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src/roles/test-linux-binary/tasks/main.yml': line 49, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Setting heartbeat_file\n ^ here\n" } ```
##### `make batch`
script returned exit code 2
``` [2021-06-18T14:12:55.796Z] Running in /var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200/src [2021-06-18T14:12:56.187Z] Recording test results [2021-06-18T14:12:56.356Z] + make clean [2021-06-18T14:12:56.356Z] vagrant destroy -f [2021-06-18T14:12:56.538Z] [Checks API] No suitable checks publisher found. [2021-06-18T14:12:56.660Z] Archiving artifacts [2021-06-18T14:12:58.174Z] + make clean [2021-06-18T14:12:58.174Z] vagrant destroy -f [2021-06-18T14:13:04.076Z] ==> tester-ubuntu2004-64: Forcing shutdown of VM... [2021-06-18T14:13:04.536Z] ==> tester-ubuntu2004-64: VM not created. Moving on... [2021-06-18T14:13:04.536Z] ==> tester-debian10-64: VM not created. Moving on... [2021-06-18T14:13:04.536Z] ==> tester-win19-64: VM not created. Moving on... [2021-06-18T14:13:04.536Z] ==> tester-centos8-64: VM not created. Moving on... [2021-06-18T14:13:04.536Z] ==> tester-awslinux2: VM not created. Moving on... [2021-06-18T14:13:04.536Z] ==> tester-ubuntu1804-64: VM not created. Moving on... [2021-06-18T14:13:04.536Z] ==> tester-sles12-64: VM not created. Moving on... [2021-06-18T14:13:04.536Z] ==> tester-debian9-64: VM not created. Moving on... [2021-06-18T14:13:04.536Z] ==> tester-awslinux: VM not created. Moving on... [2021-06-18T14:13:05.269Z] ==> tester-win12-64: Forcing shutdown of VM... [2021-06-18T14:13:05.530Z] ==> tester-ubuntu2004-64: Destroying VM and associated drives... [2021-06-18T14:13:06.719Z] ==> tester-win12-64: Destroying VM and associated drives... [2021-06-18T14:13:06.980Z] ==> tester-debian10-64: Forcing shutdown of VM... [2021-06-18T14:13:08.168Z] ==> tester-centos7-64: VM not created. Moving on... [2021-06-18T14:13:08.168Z] ==> tester-debian8-64: VM not created. Moving on... [2021-06-18T14:13:08.168Z] Makefile:71: recipe for target 'clean' failed [2021-06-18T14:13:08.168Z] make: [clean] Error 2 (ignored) [2021-06-18T14:13:08.168Z] rm -r .vagrant [2021-06-18T14:13:08.431Z] ==> tester-debian10-64: Destroying VM and associated drives... [2021-06-18T14:13:08.999Z] Failed in branch Matrix - GROUPS = 'windows' [2021-06-18T14:13:09.131Z] ==> tester-win19-64: VM not created. Moving on... [2021-06-18T14:13:09.131Z] ==> tester-centos8-64: VM not created. Moving on... [2021-06-18T14:13:09.830Z] ==> tester-awslinux2: VM not created. Moving on... [2021-06-18T14:13:10.528Z] ==> tester-ubuntu1804-64: Forcing shutdown of VM... [2021-06-18T14:13:11.980Z] ==> tester-ubuntu1804-64: Destroying VM and associated drives... [2021-06-18T14:13:12.681Z] ==> tester-sles12-64: VM not created. Moving on... [2021-06-18T14:13:13.382Z] ==> tester-debian9-64: Forcing shutdown of VM... [2021-06-18T14:13:14.840Z] ==> tester-debian9-64: Destroying VM and associated drives... [2021-06-18T14:13:14.840Z] ==> tester-awslinux: VM not created. Moving on... [2021-06-18T14:13:15.541Z] ==> tester-win12-64: VM not created. Moving on... [2021-06-18T14:13:15.541Z] ==> tester-centos7-64: VM not created. Moving on... [2021-06-18T14:13:16.245Z] ==> tester-debian8-64: Forcing shutdown of VM... [2021-06-18T14:13:16.947Z] ==> tester-debian8-64: Destroying VM and associated drives... [2021-06-18T14:13:17.985Z] Makefile:71: recipe for target 'clean' failed [2021-06-18T14:13:17.985Z] make: [clean] Error 2 (ignored) [2021-06-18T14:13:17.985Z] rm -r .vagrant [2021-06-18T14:13:18.720Z] Failed in branch Matrix - GROUPS = 'debian' [2021-06-18T14:13:19.357Z] Running on Jenkins in /var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200 [2021-06-18T14:13:19.611Z] [INFO] getVaultSecret: Getting secrets [2021-06-18T14:13:19.644Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID [2021-06-18T14:13:20.336Z] + chmod 755 generate-build-data.sh [2021-06-18T14:13:20.336Z] + ./generate-build-data.sh https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/ https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/runs/7 FAILURE 1095790 [2021-06-18T14:13:20.336Z] INFO: curl https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/runs/7/steps/?limit=10000 -o steps-info.json [2021-06-18T14:13:21.679Z] INFO: curl https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/runs/7/tests/?status=FAILED -o tests-errors.json [2021-06-18T14:13:21.930Z] INFO: curl https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/runs/7/log/ -o pipeline-log.txt [2021-06-18T14:13:21.930Z] INFO: curl https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200// -o job-info.json [2021-06-18T14:13:22.180Z] jq: error (at job-info.json:0): Cannot index string with string "_links" [2021-06-18T14:13:22.180Z] jq: error (at job-info.json:0): Cannot index string with string "_class" [2021-06-18T14:13:22.180Z] jq: error (at job-info.json:0): Cannot index string with string "downloadable" [2021-06-18T14:13:22.180Z] jq: error (at job-info.json:0): Cannot index string with string "id" [2021-06-18T14:13:22.180Z] jq: error (at job-info.json:0): Cannot index string with string "url" [2021-06-18T14:13:22.180Z] jq: error (at job-info.json:21): Cannot index boolean with string "author" [2021-06-18T14:13:22.180Z] jq: error (at job-info.json:21): Cannot index boolean with string "author" [2021-06-18T14:13:22.180Z] INFO: curl https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/runs/7/changeSet/ -o changeSet-info.json [2021-06-18T14:13:22.430Z] jq: error (at changeSet-info.json:30): Cannot index array with string "_links" [2021-06-18T14:13:22.431Z] jq: error (at changeSet-info.json:30): Cannot index array with string "_class" [2021-06-18T14:13:22.431Z] jq: error (at changeSet-info.json:30): Cannot index array with string "actions" [2021-06-18T14:13:22.431Z] jq: error (at changeSet-info.json:30): Cannot index array with string "latestRun" [2021-06-18T14:13:22.431Z] jq: error (at changeSet-info.json:30): Cannot index array with string "permissions" [2021-06-18T14:13:22.431Z] jq: error (at changeSet-info.json:30): Cannot index array with string "parameters" [2021-06-18T14:13:22.431Z] INFO: fetchAndPrepareArtifactsInfo (see artifacts-info.json) [2021-06-18T14:13:22.431Z] INFO: curl https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/runs/7/artifacts/ -o artifacts-info.json [2021-06-18T14:13:22.681Z] INFO: fetchAndPrepareTestsInfo (see tests-info.json) [2021-06-18T14:13:22.681Z] INFO: curl https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/runs/7/tests/?limit=10000000 -o tests-info.json [2021-06-18T14:13:26.803Z] INFO: fetchAndPrepareTestSummaryReport (see tests-summary.json) [2021-06-18T14:13:26.803Z] INFO: curl https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/runs/7/blueTestSummary/ -o tests-summary.json [2021-06-18T14:13:26.803Z] INFO: fetchAndPrepareBuildInfo (see build-info.json) [2021-06-18T14:13:26.803Z] INFO: curl https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/runs/7/ -o build-info.json [2021-06-18T14:13:27.063Z] Archiving artifacts [2021-06-18T14:13:27.096Z] Timeout set to expire in 5 min 0 sec [2021-06-18T14:13:27.379Z] Archiving artifacts [2021-06-18T14:13:27.600Z] [WARN] notifyIfPossible: could not fetch the nextBuild. [2021-06-18T14:13:27.699Z] Copied 1 artifact from "Beats » Pipeline for beats-tester » PR-200" build number 6 [2021-06-18T14:13:28.755Z] Archiving artifacts [2021-06-18T14:13:28.786Z] Timeout set to expire in 5 min 0 sec [2021-06-18T14:13:28.878Z] [INFO] getVaultSecret: Getting secrets [2021-06-18T14:13:28.912Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID [2021-06-18T14:13:29.275Z] [INFO] sendDataToElasticsearch: sending data... [2021-06-18T14:13:31.151Z] [INFO] getVaultSecret: Getting secrets [2021-06-18T14:13:31.183Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID [2021-06-18T14:13:31.372Z] [INFO] sendDataToElasticsearch: sending data... [2021-06-18T14:13:32.062Z] [INFO] getVaultSecret: Getting secrets [2021-06-18T14:13:32.093Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID [2021-06-18T14:13:32.298Z] [INFO] sendDataToElasticsearch: sending data... [2021-06-18T14:13:32.461Z] Running on Jenkins in /var/lib/jenkins/workspace/Beats_beats-tester-mbp_PR-200 [2021-06-18T14:13:32.485Z] [INFO] getVaultSecret: Getting secrets [2021-06-18T14:13:32.514Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID [2021-06-18T14:13:33.006Z] + chmod 755 generate-build-data.sh [2021-06-18T14:13:33.006Z] + ./generate-build-data.sh https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/ https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/runs/7 FAILURE 1108461 [2021-06-18T14:13:33.006Z] INFO: curl https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/runs/7/steps/?limit=10000 -o steps-info.json [2021-06-18T14:13:34.349Z] INFO: curl https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/beats-tester-mbp/PR-200/runs/7/tests/?status=FAILED -o tests-errors.json ```
I think the change we need is similar to this line that edits the file contained in the installation package rather than the template.
/test
What
Set enabled:true since it was disabled in https://github.com/elastic/beats/commit/e2bfa101ba74d1c0836c329dcaf26482a2208be1
Issues
Closes #198
Thanks @andrewvc for the debugging