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 upgrade e2e test #9667

Open
latin-panda opened this issue Nov 25, 2024 · 1 comment
Open

Flaky upgrade e2e test #9667

latin-panda opened this issue Nov 25, 2024 · 1 comment
Labels
Flaky Indicates a flaky or unreliable test Type: Technical issue Improve something that users won't notice

Comments

@latin-panda
Copy link
Contributor

Describe the issue

I've seen a couple of PRs failing in this test; rerunning it makes it pass. It didn't have any allure report/screenshots but here is the failing test:

Image

Describe the improvement you'd like
Maybe it needs to give some time for the label to appear.

Describe alternatives you've considered

@latin-panda latin-panda added Flaky Indicates a flaky or unreliable test Type: Technical issue Improve something that users won't notice labels Nov 25, 2024
@mrjones-plip
Copy link
Contributor

noting I hit this same error (for both Upgrade from 4.2.4 and Upgrade from latest) a bunch and pasting in the error so it can be searched for:

[chrome 131.0.6778.85 linux #0-0] » /tests/e2e/upgrade/upgrade.wdio-spec.js
[chrome 131.0.6778.85 linux #0-0] Performing an upgrade
[chrome 131.0.6778.85 linux #0-0]    ✓ should have an upgrade_log after installing the app, without logs upgrade is aborted
[chrome 131.0.6778.85 linux #0-0]    ✓ should have valid semver after installing
[chrome 131.0.6778.85 linux #0-0]    ✖ should upgrade to current branch
[chrome 131.0.6778.85 linux #0-0]
[chrome 131.0.6778.85 linux #0-0] 2 passing (1m 5.4s)
[chrome 131.0.6778.85 linux #0-0] 1 failing
[chrome 131.0.6778.85 linux #0-0]
[chrome 131.0.6778.85 linux #0-0] 1) Performing an upgrade should upgrade to current branch
[chrome 131.0.6778.85 linux #0-0] expected '4.15.0-validate-docker-helper-version' to include '4.14.0'      
      actual expected
      
      '4.15.0-validate-docker-helper-version'undefined
      
[chrome 131.0.6778.85 linux #0-0] AssertionError: expected '4.15.0-validate-docker-helper-version' to include '4.14.0'
[chrome 131.0.6778.85 linux #0-0]     at Context.<anonymous> (/home/runner/work/cht-core/cht-core/tests/e2e/upgrade/upgrade.wdio-spec.js:93:41)

@lorerod lorerod removed their assignment Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Flaky Indicates a flaky or unreliable test Type: Technical issue Improve something that users won't notice
Projects
Status: Todo
Development

No branches or pull requests

3 participants