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

Flaky odo logs test: should successfully show logs of the running component #6619

Closed
rm3l opened this issue Feb 22, 2023 · 3 comments
Closed
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering flake Categorizes issue or PR as related to a flaky test. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@rm3l
Copy link
Member

rm3l commented Feb 22, 2023

/kind bug
/area testing

  Expected
      <string>: main: Wed Feb 22 12:34:48 UTC 2023 - this is infinite while loop
      main: Wed Feb 22 12:34:53 UTC 2023 - this is infinite while loop
      main: Wed Feb 22 12:34:58 UTC 2023 - this is infinite while loop
      main: Wed Feb 22 12:35:03 UTC 2023 - this is infinite while loop
      main: Wed Feb 22 12:35:08 UTC 2023 - this is infinite while loop
      main: Wed Feb 22 12:35:13 UTC 2023 - this is infinite while loop
      runtime: npm notice created a lockfile as package-lock.json. You should commit this file.
      runtime: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
      runtime: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
      runtime: npm WARN node-echo@0.0.1 No repository field.
      runtime: npm WARN node-echo@0.0.1 No license field.
      runtime: 
      runtime: added 32 packages from 28 contributors and audited 33 packages in 2.29s
      runtime: 
      runtime: 3 packages are looking for funding
      runtime:   run `npm fund` for details
      runtime: 
      runtime: found 0 vulnerabilities
      runtime: 
      runtime: 
      runtime: > node-echo@0.0.1 start /projects
      runtime: > node server.js
      runtime: 
      runtime: Server running on 0.0.0.0:8080
      main[1]: Wed Feb 22 12:35:08 UTC 2023 - this is infinite while loop
      main[1]: Wed Feb 22 12:35:13 UTC 2023 - this is infinite while loop
      
  to contain substring
      <string>: main[2]:
  In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/3293/tests/helper/helper_generic.go:79

...

Summarizing 1 Failure:
  [FAIL] odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode [It] should successfully show logs of the running component
  C:/Users/Administrator.ANSIBLE-TEST-VS/3293/tests/helper/helper_generic.go:79

Ran 414 of 771 Specs in 1067.107 seconds
FAIL! -- 413 Passed | 1 Failed | 0 Pending | 357 Skipped

Any logs, error output, etc?

@openshift-ci openshift-ci bot added kind/bug Categorizes issue or PR as related to a bug. area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering labels Feb 22, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Feb 22, 2023
@rm3l rm3l added this to odo Project Feb 22, 2023
@valaparthvi
Copy link
Contributor

/kind flake

@openshift-ci openshift-ci bot added the flake Categorizes issue or PR as related to a flaky test. label Mar 6, 2023
@kadel kadel removed the kind/bug Categorizes issue or PR as related to a bug. label Mar 10, 2023
@rm3l rm3l mentioned this issue Apr 20, 2023
3 tasks
@github-actions
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 10, 2023
@github-actions
Copy link
Contributor

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jul 10, 2023
@github-project-automation github-project-automation bot moved this to Done ✅ in odo Project Jul 10, 2023
@rm3l rm3l closed this as not planned Won't fix, can't repro, duplicate, stale Sep 18, 2023
@rm3l rm3l removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering flake Categorizes issue or PR as related to a flaky test. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
Archived in project
Development

No branches or pull requests

3 participants