-
-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flaky tests in development #4557
Comments
on test on seed see full log here but interestingly I can't reproduce this when running the test on that seed locally This is probably the same error mentioned in issue #4381 on seed 50836 |
stacktraceDEPRECATION WARNING: `Rails.application.secrets` is deprecated in favor of `Rails.application.credentials` and will be removed in Rails 7.2. (called from at /Users/josh.nichols/workspace/human-essentials/config/environment.rb:5) DEPRECATION WARNING: `Rails.application.secrets` is deprecated in favor of `Rails.application.credentials` and will be removed in Rails 7.2. (called from at /Users/josh.nichols/workspace/human-essentials/config/environment.rb:5) Bisect started using options: "--seed 64284" Running suite to find failures.../Users/josh.nichols/.local/share/mise/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/pg-1.5.6/lib/pg/connection.rb:695: [BUG] Segmentation fault at 0x0000000100a84ae4 ruby 3.2.2 (2023-03-30 revision e51014f9c0) [arm64-darwin23] |
bringing this to the attention of @elasticspoon, who has been doing a lot of work on making our tests less flakey lately. |
Adding another flaky one to the list:
can't reproduce locally run log here |
and another one: seed 30346 can't reproduce locally run log here |
this test also times out sometimes seed 42531 run log here |
and another one seed 61879 run log here |
this one too seed 20328 run log here |
and this one seed 61006 run log here |
I followed the contributing guide, and wanted to run the specs with
bin/rspec
. I got "lucky" and had a few tests flake:I re-ran it, and the tests pass. They also seem to pass on their own.
It seemed to be very specific to the seed
64284
, where it fails with--seed 64284
but passes without it, which makes me think it is order dependent.I'm doing some more testing to make sure it is consistent, and to narrow down a reproducible case with
--bisect
, but figured I'd log it in case anyone else saw itThe text was updated successfully, but these errors were encountered: