Gitlab ci started failing without changes

:hugs: Please help fill in this template with all the details to help others help you more efficiently. Use formatting blocks for code, config, logs and ensure to remove sensitive data.

Problem to solve

Describe your question in as much detail as possible:

we have a very simple ruby CI pipeline that runs rspec on the test stage. Until now it was working but now without any change it fails without even running the script on the test stage. I thought it was the branch I was testing on, but even re-running the previous pipeline in main (that succeeded) now fails in the same way. I thought it could’ve been a problem in our image, so I reverted to the standard ruby:3.2 with the exact same result.

Other stages work, but for some reason the test stage is not running.

  • What are you seeing, and how does that differ from what you expect to see?

Pipeline fails at the test stage without running the script

  • Consider including screenshots, error messages, and/or other helpful visuals

Steps to reproduce

Which troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?

  • Create a new ruby+rspec project
  • add the ci config above
  • try to run the pipeline

Configuration

Add the CI/CD configuration from .gitlab-ci.yml and other configuration if relevant (e.g. docker-compose.yml). Alternatively, create a public GitLab.com example project that provides all necessary files to reproduce the question.

image: ruby:3.2

variables:
  BUNDLE_PATH: vendor/ruby

cache:
  key: $CI_PROJECT_NAME
  paths:
    - vendor/ruby

before_script:
  - ruby -v
  - gem install bundler --no-document
  - bundle config set --local path 'vendor'
  - bundle install --jobs $(nproc) "${FLAGS[@]}"

run_rspec:
  stage: test
  script:
    - bundle --version
    - bundle exec rspec --format p --format RspecJunitFormatter --out rspec.xml
  rules:
    - if: $CI_COMMIT_BRANCH
  coverage: /^Coverage.* LOC \((\d+.\d+%)\) covered./

Versions

Please select whether options apply, and add the version information.

  • Self-managed
  • GitLab.com SaaS
  • Self-hosted Runners

Versions

Helpful resources

  1. Before opening a new topic, make sure to search for keywords in the forum search
  2. Check the GitLab Runner and GitLab projects for existing issues. If you encounter a bug, please create a bug report issue.
  3. Troubleshooting docs: GitLab Runner, self-managed GitLab instances.

Thanks for taking the time to be thorough in your request, it really helps! :blush:

nevermind. it was the ruby version changed to 3.2.4, it was right there at the end of the logs, but because it was not marked as error I just didn’t read it.