Skip to content

test: set yarn testunit concurrency to 1 for improved stability#38939

Merged
ggazzo merged 1 commit intodevelopfrom
test/concurrency
Feb 23, 2026
Merged

test: set yarn testunit concurrency to 1 for improved stability#38939
ggazzo merged 1 commit intodevelopfrom
test/concurrency

Conversation

@ggazzo
Copy link
Copy Markdown
Member

@ggazzo ggazzo commented Feb 23, 2026 •
edited by atlassian bot
Loading

A temporary fix to prevent tests from running simultaneously, causing delays, and resulting in failure.

Proposed changes (including videos or screenshots)

Issue(s)

Steps to test or reproduce

Further comments

Summary by CodeRabbit

  • Chores
    • Adjusted unit test execution configuration to enhance test reliability and consistency.

Task: ARCH-1984

@dionisio-bot
Copy link
Copy Markdown
Contributor

dionisio-bot bot commented Feb 23, 2026 •
edited
Loading

Looks like this PR is not ready to merge, because of the following issues:

  • This PR is missing the 'stat: QA assured' label
  • This PR is targeting the wrong base branch. It should target 8.3.0, but it targets 8.2.0

Please fix the issues and try again

If you have any trouble, please check the PR guidelines

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Feb 23, 2026

⚠️ No Changeset found

Latest commit: 37e8b1e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Feb 23, 2026 •
edited
Loading

Walkthrough

The CI unit test workflow has been modified to execute unit tests with an explicit concurrency limit of 1, changing from yarn testunit to yarn testunit --concurrency=1.

Changes

Cohort / File(s) Summary
CI Workflow Configuration
.github/workflows/ci-test-unit.yml		 Modified the Unit Test step to add --concurrency=1 flag, enforcing sequential test execution instead of default parallel behavior.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop through the pipeline so fine,
Tests now march in a single-file line,
No racing, no chaos, just order sublime,
One thread at a time, keeping CI on time! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: setting yarn testunit concurrency to 1 for improved stability, which directly matches the single-line modification in the CI workflow file.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@ggazzo ggazzo changed the title chore(ci): set yarn testunit concurrency to 1 for improved stability test: set yarn testunit concurrency to 1 for improved stability Feb 23, 2026
@ggazzo ggazzo added this to the 8.3.0 milestone Feb 23, 2026
@ggazzo ggazzo marked this pull request as ready for review February 23, 2026 16:26
@ggazzo ggazzo requested a review from a team as a code owner February 23, 2026 16:26
cubic-dev-ai[bot]
cubic-dev-ai bot reviewed Feb 23, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

No issues found across 1 file

@codecov
Copy link
Copy Markdown

codecov bot commented Feb 23, 2026 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.63%. Comparing base (133da0b) to head (37e8b1e).
⚠️ Report is 4 commits behind head on develop.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop   #38939      +/-   ##
===========================================
+ Coverage    70.56%   70.63%   +0.07%     
===========================================
  Files         3189     3189              
  Lines       112702   112716      +14     
  Branches     20429    20429              
===========================================
+ Hits         79526    79615      +89     
+ Misses       31115    31049      -66     
+ Partials      2061     2052       -9
Flag Coverage Δ
e2e 60.38% <ø> (+<0.01%) ⬆️
e2e-api 47.80% <ø> (+0.01%) ⬆️
unit 71.19% <ø> (-0.36%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ggazzo
Copy link
Copy Markdown
Member Author

ggazzo commented Feb 23, 2026

/jira ARCH-1935

@ggazzo ggazzo merged commit 18a1018 into develop Feb 23, 2026
79 of 82 checks passed
@ggazzo ggazzo deleted the test/concurrency branch February 23, 2026 18:12
@ahmed-n-abdeltwab ahmed-n-abdeltwab mentioned this pull request Feb 23, 2026
Draft
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cubic-dev-ai cubic-dev-ai[bot] cubic-dev-ai[bot] left review comments

@tassoevan tassoevan tassoevan approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

8.3.0

Development

Successfully merging this pull request may close these issues.

2 participants

@ggazzo @tassoevan