Skip to content
This repository was archived by the owner on Sep 17, 2024. It is now read-only.

chore: use trace level in logs#2130

Merged
mdelapenya merged 3 commits intoelastic:mainfrom
mdelapenya:log-level-trace
Mar 1, 2022
Merged

chore: use trace level in logs#2130
mdelapenya merged 3 commits intoelastic:mainfrom
mdelapenya:log-level-trace

Conversation

@mdelapenya
Copy link
Copy Markdown
Contributor

@mdelapenya mdelapenya commented Feb 10, 2022

What does this PR do?

It uses TRACE log level on CI executions, updating the generated shell script that triggers the tests on the AWS instances.

Finally it sets the value at the Jenkinsfile too

Why is it important?

Add more logs for troubleshooting the errors

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have run the Unit tests (make unit-test), and they are passing locally
  • I have run the End-2-End tests for the suite I'm working on, and they are passing locally
  • I have noticed new Go dependencies (run make notice in the proper directory)

Author's Checklist

  • Updated Jenkinsfile
  • Updates shell scripts generated by Ansible to be sent to the VMs
  • I think we should simply read the Jenkins parameter and pass it to the Ansible execution to generate the scripts with what we defined in the build

@mdelapenya mdelapenya added backport-v7.16.0 Automated backport with mergify backport-v7.17.0 Automated backport with mergify backport-v8.0.0 Automated backport with mergify labels Feb 10, 2022
@mdelapenya mdelapenya self-assigned this Feb 10, 2022
@mdelapenya mdelapenya requested a review from a team February 10, 2022 11:08
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Feb 10, 2022 •
edited
Loading

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-03-01T06:22:40.505+0000

  • Duration: 50 min 25 sec

Test stats 🧪

Test Results
Failed 1
Passed 271
Skipped 0
Total 272

Test errors 1

Expand to view the tests failures

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from running pod – elastic-agent standalone
    Expand to view the error details

     Step "elastic-agent" collects events with "kubernetes.pod.name:a-pod": context deadline exceeded

  • no stacktrace

Steps errors 2

Expand to view the steps failures

Shell Script
  • Took 17 min 25 sec . View more details here
  • Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2130-3-fefd02d5-7eae-4787-b45c-d6209bb5fb56/e2essh admin@18.223.164.93 -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "elastic-agent && ~@nightly && ~@skip:amd64" '
Archive the artifacts
  • Took 0 min 0 sec . View more details here
  • Description: [2022-03-01T07:12:58.407Z] Archiving artifacts script returned exit code 2

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors 1

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

  • Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from running pod – elastic-agent standalone

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Feb 28, 2022

This pull request is now in conflict. Could you fix it @mdelapenya? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b log-level-trace upstream/log-level-trace
git merge upstream/main
git push upstream log-level-trace

@mdelapenya mdelapenya added backport-v8.1.0 Automated backport with mergify and removed backport-v7.16.0 Automated backport with mergify labels Feb 28, 2022
@mdelapenya mdelapenya merged commit d393d27 into elastic:main Mar 1, 2022
mergify bot pushed a commit that referenced this pull request Mar 1, 2022
@mdelapenya
chore: use trace level in logs (#2130)
e4ea351 
(cherry picked from commit d393d27)
@mergify mergify bot mentioned this pull request Mar 1, 2022
Merged
mergify bot pushed a commit that referenced this pull request Mar 1, 2022
@mdelapenya
chore: use trace level in logs (#2130)
e9dd82a 
(cherry picked from commit d393d27)
@mergify mergify bot mentioned this pull request Mar 1, 2022
Merged
mergify bot pushed a commit that referenced this pull request Mar 1, 2022
@mdelapenya
chore: use trace level in logs (#2130)
b69db12 
(cherry picked from commit d393d27)

# Conflicts:
#	.ci/Jenkinsfile
@mergify mergify bot mentioned this pull request Mar 1, 2022
Merged
mdelapenya added a commit that referenced this pull request Mar 1, 2022
@mergify @mdelapenya
[7.17](backport #2130) chore: use trace level in logs (#2192)
364fef2 
* chore: use trace level in logs (#2130)

(cherry picked from commit d393d27)

# Conflicts:
#	.ci/Jenkinsfile

* fix: resolve conflicts

Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>
mdelapenya added a commit that referenced this pull request Mar 2, 2022
@mergify @mdelapenya
chore: use trace level in logs (#2130) (#2191)
cb362b5 
(cherry picked from commit d393d27)

Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>
mdelapenya added a commit that referenced this pull request Mar 8, 2022
@mergify @mdelapenya
chore: use trace level in logs (#2130) (#2190)
4a65e8d 
(cherry picked from commit d393d27)

Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>
@mdelapenya mdelapenya deleted the log-level-trace branch March 9, 2022 06:38
mdelapenya added a commit that referenced this pull request Mar 17, 2022
@mdelapenya
Merge branch 'main' into EricDavisX-patch-x3
47c3951 
* main: (268 commits)
  bump stack version 8.2.0-ff67d7b8 (#2242)
  ci: periodic builds for the last two minor versions (#2241)
  bump stack version 8.2.0-9bac538c (#2240)
  fix: add end-of-file line in templates (#2237)
  chore: add Christos to SSH users
  bump stack version 8.2.0-fee3b8d2 (#2234)
  Separate ES workload from Agent spec and make it req for the scenarios (#2203)
  bump stack version 8.2.0-d02c907a (#2228)
  bump stack version 8.2.0-63265ec9 (#2225)
  fix: wrong link (#2220)
  chore: define provider for each test suite (#2213)
  ci: provision e2-small workers (#2212)
  bump stack version 8.2.0-a12f7069 (#2209)
  chore: support for Oracle Linux 8 (#2208)
  bump stack version 8.2.0-190af159 (#2206)
  bump stack version 8.2.0-fdde08ec (#2200)
  bump stack version 8.2.0-43df679f (#2193)
  chore: use trace level in logs (#2130)
  bump stack version 8.2.0-bdf2ad74 (#2188)
  feat: support downloading project artifacts for the new bucket layout (#2172)
  ...
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

@mdelapenya mdelapenya

Labels

backport-v7.17.0 Automated backport with mergify backport-v8.0.0 Automated backport with mergify backport-v8.1.0 Automated backport with mergify

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@mdelapenya @elasticmachine