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

fix(ex/api/stream_test): fix intermitently failing tests #2303

Merged
merged 11 commits into from
Dec 7, 2023

Conversation

firestack
Copy link
Member

@firestack firestack commented Dec 6, 2023

I tried fixing this by addressing the Bypass issue, but that didn't actually help. So instead I've decided to cut out the ServerSentEventsStage and replace it with the parse results that Api.Stream received from the tests before this change.


Asana Ticket: ⚙️ Fix false positive test failure in stream_test.ex

CI Runs Information

Number of stream_test Failures in #2303 so far
0
Total #2303 Pipeline Runs
Total #2303 Pushed Commits
11
Total #2303 CI Jobs
14
Successful #2303 Jobs
14 Successful Jobs
  1. Elixir and TypeScript CI / Build and test Elixir (pull_request) Successful in 3m
  2. Elixir and TypeScript CI / Build and test Elixir (push) Successful in 3m

  3. Elixir and TypeScript CI / Build and test Elixir (push) Successful in 3m

  4. Elixir and TypeScript CI / Build and test Elixir (push) Successful in 3m

  5. Elixir and TypeScript CI / Build and test Elixir (push) Successful in 4m

  6. Elixir and TypeScript CI / Build and test Elixir (push) Successful in 3m

  7. Elixir and TypeScript CI / Build and test Elixir (pull_request) Successful in 3m
  8. Elixir and TypeScript CI / Build and test Elixir (push) Successful in 3m

  9. Elixir and TypeScript CI / Build and test Elixir (push) Successful in 3m

  10. Elixir and TypeScript CI / Build and test Elixir (push) Successful in 4m

  11. Elixir and TypeScript CI / Build and test Elixir (push) Successful in 3m

  12. Elixir and TypeScript CI / Build and test Elixir (push) Successful in 3m

  13. Elixir and TypeScript CI / Build and test Elixir (push) Successful in 3m
  14. Elixir and TypeScript CI / Build and test Elixir (pull_request) Successful in 3m

@firestack firestack self-assigned this Dec 6, 2023

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

@firestack firestack marked this pull request as ready for review December 7, 2023 03:14
@firestack firestack requested a review from a team as a code owner December 7, 2023 03:14
Copy link
Member

@lemald lemald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@firestack firestack merged commit 6e5d4fc into master Dec 7, 2023
8 checks passed
@firestack firestack deleted the kf/asn/fix-bypass branch December 7, 2023 14:18
{:ok, conn} = Conn.chunk(conn, "event: ignores unexpected events\n\n")
{:ok, conn} = Conn.chunk(conn, "ignored garbled data\n\n")
{:ok, conn} = Conn.chunk(conn, "event: reset\ndata: #{Jason.encode!([data])}\n\n")
{:ok, conn} = Conn.chunk(conn, "event: add\ndata: #{Jason.encode!(data)}\n\n")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this introduce flakiness if Jason.encode! doesn't follow the same key order each time?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't believe so, because we're asserting on the type returned and the event returned, but it doesn't seem that we're asserting on any of the JSON data.

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

Successfully merging this pull request may close these issues.

3 participants