Geo::RepositoryVerification::Primary::ShardWorker #perform performs Geo::RepositoryVerification::Primary::SingleWorker for each project (FAILED - 58)1st Try error in ./ee/spec/workers/geo/repository_verification/primary/shard_worker_spec.rb:34:(Geo::RepositoryVerification::Primary::SingleWorker (class)).perform_async(1031) expected: 2 times with any arguments received: 3 times with arguments: (1031)RSpec::Retry: 2nd try ./ee/spec/workers/geo/repository_verification/primary/shard_worker_spec.rb:34ERROR: Job failed: execution took longer than 1h30m0s seconds
1st Try error in ./ee/spec/policies/epic_policy_spec.rb:53:undefined method `allow_stale_runner_pruning' for #<FactoryBot::SyntaxRunner:0x00007fb69b611940>
I think we get a lot of times this error and we have a retries for multiple tests, wich is leading to pipelines to take ling time and timout
Yeah, it seems to be the cause here. There was another interesting report at #378381 (comment 1141330955) with less spec files run so I'm trying to reproduce locally with
➜ gitlab git:(master) ✗ bin/rspec ee/spec/migrations/update_gitlab_subscriptions_start_at_post_eoa_spec.rb ee/spec/migrations/backfill_namespace_statistics_with_wiki_size_spec.rbwarning: parser/current is loading parser/ruby27, which recognizes2.7.6-compliant syntax, but you are running 2.7.5.Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.Run options: include {:focus=>true}All examples were filtered out; ignoring {:focus=>true}Test environment set up in 6.980643 secondsFFFFF!!! before_all transaction has been already rollbacked and could work incorrectly!!! before_all transaction has been already rollbacked and could work incorrectlyFailures: 1) UpdateGitlabSubscriptionsStartAtPostEoa#up when not on GitLab.com does not do any update Failure/Error: block.call StandardError: An error has occurred, this and all later migrations canceled: PG::DependentObjectsStillExist: ERROR: cannot drop table incident_management_pending_issue_escalations because other objects depend on it DETAIL: default value for column id of table gitlab_partitions_dynamic.incident_management_pending_issue_escalations_000000 depends on sequence incident_management_pending_issue_escalations_id_seq HINT: Use DROP ... CASCADE to drop the dependent objects too. # ./db/migrate/20210730194555_create_incident_management_pending_issue_escalations.rb:30:in `block in down' # ./lib/gitlab/database/with_lock_retries.rb:123:in `run_block' # ./lib/gitlab/database/with_lock_retries.rb:134:in `block in run_block_with_lock_timeout' # ./lib/gitlab/database/with_lock_retries.rb:129:in `run_block_with_lock_timeout' # ./lib/gitlab/database/with_lock_retries.rb:97:in `run' # ./lib/gitlab/database/migration_helpers.rb:451:in `with_lock_retries' # ./db/migrate/20210730194555_create_incident_management_pending_issue_escalations.rb:29:in `down' # ./lib/gitlab/database/load_balancing/connection_proxy.rb:120:in `block in write_using_load_balancer' # ./lib/gitlab/database/load_balancing/load_balancer.rb:122:in `block in read_write' # ./lib/gitlab/database/load_balancing/load_balancer.rb:193:in `retry_with_backoff' # ./lib/gitlab/database/load_balancing/load_balancer.rb:118:in `read_write' # ./lib/gitlab/database/load_balancing/connection_proxy.rb:119:in `write_using_load_balancer' # ./lib/gitlab/database/load_balancing/connection_proxy.rb:71:in `transaction' # ./lib/gitlab/database.rb:332:in `block in transaction' # ./lib/gitlab/database.rb:331:in `transaction' # ./lib/gitlab/database/migrations/lock_retry_mixin.rb:36:in `ddl_transaction' # ./spec/support/helpers/migrations_helpers.rb:133:in `block in schema_migrate_down!' # ./spec/support/helpers/migrations_helpers.rb:153:in `disable_migrations_output' # ./spec/support/helpers/migrations_helpers.rb:132:in `schema_migrate_down!' # ./ee/spec/support/helpers/ee/migrations_helpers.rb:33:in `block in schema_migrate_down!' # ./ee/spec/support/helpers/ee/migrations_helpers.rb:50:in `with_db_config' # ./ee/spec/support/helpers/ee/migrations_helpers.rb:33:in `schema_migrate_down!' # ./spec/support/migration.rb:16:in `block (2 levels) in <main>' # ------------------ # --- Caused by: --- # PG::DependentObjectsStillExist: # ERROR: cannot drop table incident_management_pending_issue_escalations because other objects depend on it # DETAIL: default value for column id of table gitlab_partitions_dynamic.incident_management_pending_issue_escalations_000000 depends on sequence incident_management_pending_issue_escalations_id_seq # HINT: Use DROP ... CASCADE to drop the dependent objects too. # ./db/migrate/20210730194555_create_incident_management_pending_issue_escalations.rb:30:in `block in down'
Actually, the spec started to failed after ee/spec/migrations/backfill_namespace_statistics_with_wiki_size_spec.rb finished in https://gitlab.com/gitlab-org/gitlab/-/jobs/3193979839#L874 (not sure why the Knapsack report only list ee/spec/migrations/update_gitlab_subscriptions_start_at_post_eoa_spec.rb and ee/spec/migrations/backfill_namespace_statistics_with_wiki_size_spec.rb?).
If you do not feel the purpose of this issue matches one of the types, you may apply the typeignore label to exclude it from type tracking metrics and future prompts.