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

Understand the scope of work required to stabilise ably cocoa tests #1279

Closed
jamienewcomb opened this issue Feb 4, 2022 · 4 comments
Closed
Assignees

Comments

@jamienewcomb
Copy link
Member

jamienewcomb commented Feb 4, 2022

We need to understand what needs to be done so the tests in ably-cocoa are stable

┆Issue is synchronized with this Jira Research by Unito

@lawrence-forooghian
Copy link
Collaborator

The internal discussion about #1278 might be worth looking at here, too.

@maratal
Copy link
Collaborator

maratal commented Feb 7, 2022

Example of unstable test - #1281

@lawrence-forooghian
Copy link
Collaborator

Our next step here will be to investigate the top 40% of test failures (#1330).

lawrence-forooghian added a commit that referenced this issue Apr 27, 2022
This will help us investigate failures as we work on
#1279.

Closes #1322.
lawrence-forooghian added a commit that referenced this issue May 3, 2022
…vability-server

(#1279) Upload crash reports to test observability server
@QuintinWillison
Copy link
Contributor

I see that there has been a lot of activity linked to this issue, however there is no clear scope or acceptance criteria that could lead to completion. I believe that since this issue was created we have a much better view of our tests, via @lawrence-forooghian's efforts around observability, as well as plenty of well-defined issues under the failing-test label. Therefore, at this point, I don't think this issue adds any value to our backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants