Investigate & Fix/Quarantine test file: /browser_ui/5_package/package_registry/maven/maven_group_level_spec.rb

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Context

The /browser_ui/5_package/package_registry/maven/maven_group_level_spec.rb spec file currently holds the 7th place of test file causing the most CI/CD pipeline failures in the last 3 months 🏅 . During those last 3 months:

1. It caused 311 MR pipeline failures (that's ~15 pipeline failures a day, each impacting our Engineers)
2. It caused 17 master pipeline failures (each potentially causing master-broken incidents)

See the Snowflake dashboard for that test file:

More info from the dashboard

1. Looking at the failures over time, we had one peak on 2024-05-28, but it still fails pipelines daily:

2. There are 5 tests failing in that file (based on the name, and the number of errors, they are likely to be related)

   • Package Maven group level endpoint without duplication setting using a ci job token pushes and pulls a maven package
   • Package Maven group level endpoint without duplication setting using a personal access token pushes and pulls a maven package
   • Package Maven group level endpoint with duplication setting when enabled allows users to publish duplicates
   • Package Maven group level endpoint without duplication setting using a project deploy token pushes and pulls a maven package
   • Package Maven group level endpoint with duplication setting when disabled prevents users from publishing duplicates

3. Looking at the recent reports, here are the failures breakdown:

Error Type	Count	% of Total	Description
Job Success Timeout	241	35.7%	QA::Page::Project::Job::Show.successful? timeouts (400s/800s)
JavaScript Reset Error	160	23.7%	Cannot read properties of undefined (reading 'reset')
RSpec Multiple Exception	122	18.1%	Cascading test failures
Repository Commit Fabrication	50	7.4%	Git pre-receive hook failures (500 errors)
Pipeline Creation Timeout	25	3.7%	Pipeline creation failed after 240s
API 500 Internal Server Error	19	2.8%	Various API endpoints returning 500
Wait Timeout	17	2.5%	Generic wait failures (60s/240s)
Package Detection	8	1.2%	Maven package not found in registry
Page Load Issues	8	1.2%	Async requests/loading icons hanging
Runner/Resource Deletion	7	1.0%	Failed to delete runners (500 errors)
UI Element Missing	4	0.6%	CSS selectors not found
Symbol Conversion	3	0.4%	no implicit conversion of Symbol into Integer
Other	11	1.6%	User/Group fabrication, login, misc

Goal

Investigate the problem ,and fix/quarantine (if appropriate).

Even if the problem was caused by an infrastructure issue, I would find it interesting to make that test more resilient to those problems (if applicable).

About the data

We started importing data in Snowflake for non-E2E tests on 2025-04-23. We don't have non-E2E tests data before that date.