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.

Sign up for GitHub

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

Jump to bottom

Flaky tests (triggered in autopkgtests on armhf) #535

Closed
2 tasks done
didrocks opened this issue Feb 2, 2024 · 1 comment
Closed
2 tasks done

Flaky tests (triggered in autopkgtests on armhf) #535

didrocks opened this issue Feb 2, 2024 · 1 comment
Assignees
@EduardGomezEscandell
Labels
bug Something isn't working jira Sync to jira

Comments

@didrocks
Copy link
Collaborator

didrocks commented Feb 2, 2024

Is there an existing issue for this?

  • I have searched the existing issues and found none that matched mine

Describe the issue

Some tests triggered races on armhf, which was a very slow VM in autopkgtests. Worth checking them so that we don’t get a pass and have to rerun the tests everytimes we are failing.

I considered them as flaky as they are all timing related.

Steps to reproduce it

Test list failing:

https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/armhf/w/wsl-pro-service/20240202_051125_c3828@/log.gz

768s --- FAIL: TestReconnection (0.00s)
768s     --- FAIL: TestReconnection/Success_connecting_after_failing_to_connect (79.91s)
768s     --- FAIL: TestReconnection/Success_connecting_after_previous_connection_dropped (86.16s)


768s --- FAIL: TestServeAndQuit (0.12s)
768s     --- FAIL: TestServeAndQuit/Success_with_graceful_quit (74.30s)
768s     --- FAIL: TestServeAndQuit/Success_with_forceful_quit (98.06s)
768s     --- FAIL: TestServeAndQuit/Success_with_double_quit (100.96s)


1124s --- FAIL: TestReconnection (0.00s)
1124s     --- FAIL: TestReconnection/Success_connecting_after_previous_connection_dropped (100.70s)

Ubuntu System information

No response

Installed versions

No response

Additional information

No response

Double check your logs

  • I have redacted any sensitive information from the logs
@didrocks didrocks added bug Something isn't working jira Sync to jira labels Feb 2, 2024
@EduardGomezEscandell EduardGomezEscandell mentioned this issue Feb 2, 2024
Merged
@EduardGomezEscandell EduardGomezEscandell self-assigned this Feb 2, 2024
EduardGomezEscandell added a commit that referenced this issue Feb 2, 2024
@EduardGomezEscandell
fix(wsl-pro-service): Increase a couple of timeouts in the tests (#538)
7cf488d 
Some tests failed in the launchpad runner. See here:
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/armhf/w/wsl-pro-service/20240202_051125_c3828@/log.gz

They are all related to require.Eventually assertions, so I increased
their timeouts. This may worsen performance when tests fail, but the
happy path remains just as fast.

Related to #535.

---

UDENG-2228
@CarlosNihelton
Copy link
Contributor

Closed by #873 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@EduardGomezEscandell EduardGomezEscandell

Labels
bug Something isn't working jira Sync to jira
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@didrocks @CarlosNihelton @EduardGomezEscandell