Investigate why Sequencing Server Tests are Flaky

Open
#1,636 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
testing-qa

Research direction

Start by reviewing the Sequencing Server Test failures in the two linked GitHub Actions runs and compare their logs and failure patterns. Trace the failing tests to the relevant test and server entry points, then identify and resolve the source of the flakiness. Done means the Sequencing Server Tests run reliably without reproducing the reported intermittent failures.

Written by the indexing model from the issue text.

Description

investigate test

Title is an apt description. The Sequencing Server Tests have been flaky as of late. Completion of this ticket involves investigating why and resolving it.

Example Test Runs where this occurred:
https://github.com/NASA-AMMOS/aerie/actions/runs/13063337782/attempts/1
https://github.com/NASA-AMMOS/aerie/actions/runs/13035929860/attempts/1

Dominant language
Java
Stars
128
Forks
33
Avg merge
1d 17h
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NASA-AMMOS/plandev

All issues in NASA-AMMOS/plandev

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.