Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #316617 > unrolled thread

Bug#1006981: rails: flaky autopkgtest on some ci.d.n architectures

Started byPaul Gevers <elbrus@debian.org>
First post2022-03-09 22:00 +0100
Last post2022-06-21 13:00 +0200
Articles 5 — 2 participants

Back to article view | Back to linux.debian.bugs.rc

Contents

  Bug#1006981: rails: flaky autopkgtest on some ci.d.n architectures Paul Gevers <elbrus@debian.org> - 2022-03-09 22:00 +0100
    Bug#1006981: marked as done (rails: flaky autopkgtest on some  ci.d.n architectures) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-04-30 15:30 +0200
    Processed: Re: Bug#1006981: fixed in rails 2:6.1.4.6+dfsg-2 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-05-12 10:30 +0200
    Bug#1006981: fixed in rails 2:6.1.4.6+dfsg-2 Paul Gevers <elbrus@debian.org> - 2022-05-12 10:30 +0200
    Bug#1006981: marked as done (rails: flaky autopkgtest on some  ci.d.n architectures) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-06-21 13:00 +0200

#316617 — Bug#1006981: rails: flaky autopkgtest on some ci.d.n architectures

FromPaul Gevers <elbrus@debian.org>
Date2022-03-09 22:00 +0100
SubjectBug#1006981: rails: flaky autopkgtest on some ci.d.n architectures
Message-ID<DZbzA-F0A-7@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Source: rails
Version: 2:6.0.3.5+dfsg-1
Severity: serious
User: debian-ci@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on amd64 and 
armhf because it was showing up as a regression for the upload of 
ruby-defaults. I noticed that the test regularly fails on some 
architectures, notably armhf (which always runs on a host with lost of 
cores and RAM) and amd64 (where we have one host with lots of cores and 
RAM).

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/armhf/r/rails/19826102/log.gz

Failure:
ActiveSupport::Cache::RedisCacheStoreTests::RedisCacheStoreCommonBehaviorTest#test_fetch_multi_without_expires_in 
[/tmp/autopkgtest-lxc.0k72y7c9/downtmp/build.89X/src/activesupport/test/cache/behaviors/cache_store_behavior.rb:135]:
--- expected
+++ actual
@@ -1 +1 @@
-{"foo"=>"bar", "fu"=>"fufu", "fud"=>"biz"}
+{"foo"=>"foofoo", "fu"=>"fufu", "fud"=>"biz"}



https://ci.debian.net/data/autopkgtest/testing/amd64/r/rails/19565734/log.gz

Failure:
ActiveSupport::Cache::RedisCacheStoreTests::RedisCacheStoreCommonBehaviorTest#test_large_string_with_compress_false 
[/tmp/autopkgtest-lxc.1wz7jlg5/downtmp/build.gWN/src/activesupport/test/cache/behaviors/cache_store_behavior.rb:226]:
--- expected
+++ actual
@@ -1 +1 @@
-"00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
+nil

[toc] | [next] | [standalone]

#319431 — Bug#1006981: marked as done (rails: flaky autopkgtest on some ci.d.n architectures)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2022-04-30 15:30 +0200
SubjectBug#1006981: marked as done (rails: flaky autopkgtest on some ci.d.n architectures)
Message-ID<EhVkB-ce3K-5@gated-at.bofh.it>
In reply to#316617

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sat, 30 Apr 2022 13:20:23 +0000
with message-id <E1nkn1L-000EUY-FV@fasolo.debian.org>
and subject line Bug#1006981: fixed in rails 2:6.1.4.6+dfsg-2
has caused the Debian Bug report #1006981,
regarding rails: flaky autopkgtest on some ci.d.n architectures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1006981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006981
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#319868 — Processed: Re: Bug#1006981: fixed in rails 2:6.1.4.6+dfsg-2

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2022-05-12 10:30 +0200
SubjectProcessed: Re: Bug#1006981: fixed in rails 2:6.1.4.6+dfsg-2
Message-ID<EmcmR-eWee-5@gated-at.bofh.it>
In reply to#316617
Processing control commands:

> reopen -1
Bug #1006981 {Done: Antonio Terceiro <terceiro@debian.org>} [src:rails] rails: flaky autopkgtest on some ci.d.n architectures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions rails/2:6.1.4.6+dfsg-2.
> found -1 2:6.1.4.6+dfsg-2
Bug #1006981 [src:rails] rails: flaky autopkgtest on some ci.d.n architectures
Marked as found in versions rails/2:6.1.4.6+dfsg-2.

-- 
1006981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006981
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#319869 — Bug#1006981: fixed in rails 2:6.1.4.6+dfsg-2

FromPaul Gevers <elbrus@debian.org>
Date2022-05-12 10:30 +0200
SubjectBug#1006981: fixed in rails 2:6.1.4.6+dfsg-2
Message-ID<EmcmR-eWee-1@gated-at.bofh.it>
In reply to#316617

[Multipart message — attachments visible in raw view] — view raw

Control: reopen -1
Control: found -1 2:6.1.4.6+dfsg-2

On Sat, 30 Apr 2022 13:20:23 +0000 Debian FTP Masters 
<ftpmaster@ftp-master.debian.org> wrote:
>  rails (2:6.1.4.6+dfsg-2) unstable; urgency=medium
>  .
>    * Skip flaky tests (Closes: #1006981)

Looks like there are more flaky tests:

https://ci.debian.net/data/autopkgtest/testing/armhf/r/rails/21412101/log.gz

/usr/bin/ruby3.0 -w -I"lib" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/cache/stores/redis_cache_store_test.rb" --seed=0
Run options: --seed=0

# Running:

........................................................................................................S.........................................F

Failure:
ActiveSupport::Cache::RedisCacheStoreTests::RedisCacheStoreCommonBehaviorTest#test_delete 
[/tmp/autopkgtest-lxc.ccf2mxu8/downtmp/build.j4S/src/activesupport/test/cache/behaviors/cache_store_behavior.rb:371]:
Expected false to be truthy.

rails test 
tmp/autopkgtest-lxc.ccf2mxu8/downtmp/build.j4S/src/activesupport/test/cache/behaviors/cache_store_behavior.rb:369

...............

Finished in 3.461934s, 46.7947 runs/s, 95.0336 assertions/s.
162 runs, 329 assertions, 1 failures, 0 errors, 1 skips

You have skipped tests. Run with --verbose for details.
rake aborted!
Command failed with status (1): [ruby -w -I"lib" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/cache/stores/redis_cache_store_test.rb" --seed=0]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/testtask.rb:130:in 
`block (3 levels) in define'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/file_utils.rb:57:in 
`sh'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/file_utils.rb:104:in 
`ruby'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/testtask.rb:117:in 
`block (2 levels) in define'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/file_utils_ext.rb:58:in 
`verbose'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/testtask.rb:111:in 
`block in define'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:281:in 
`block in execute'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:281:in 
`each'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:281:in 
`execute'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:219:in 
`block in invoke_with_call_chain'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:199:in 
`synchronize'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:199:in 
`invoke_with_call_chain'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:188:in 
`invoke'
/tmp/autopkgtest-lxc.ccf2mxu8/downtmp/build.j4S/src/activesupport/Rakefile:17:in 
`block in <top (required)>'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:281:in 
`block in execute'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:281:in 
`each'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:281:in 
`execute'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:219:in 
`block in invoke_with_call_chain'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:199:in 
`synchronize'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:199:in 
`invoke_with_call_chain'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:188:in 
`invoke'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:160:in 
`invoke_task'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:116:in 
`block (2 levels) in top_level'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:116:in 
`each'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:116:in 
`block in top_level'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:125:in 
`run_with_threads'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:110:in 
`top_level'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:83:in 
`block in run'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:186:in 
`standard_exception_handling'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:80:in 
`run'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in 
`<top (required)>'
/usr/bin/rake:25:in `load'
/usr/bin/rake:25:in `<main>'
Tasks: TOP => test:cache_stores:redis:ruby
cd -
Failed tests: activesupport:test
mv ./.gem2deb.Gemfile.lock Gemfile.lock

[toc] | [prev] | [next] | [standalone]

#321785 — Bug#1006981: marked as done (rails: flaky autopkgtest on some ci.d.n architectures)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2022-06-21 13:00 +0200
SubjectBug#1006981: marked as done (rails: flaky autopkgtest on some ci.d.n architectures)
Message-ID<EAJLX-6fsi-5@gated-at.bofh.it>
In reply to#316617

[Multipart message — attachments visible in raw view] — view raw

Your message dated Tue, 21 Jun 2022 10:49:11 +0000
with message-id <E1o3bRX-0000if-GW@fasolo.debian.org>
and subject line Bug#1006981: fixed in rails 2:6.1.4.7+dfsg-2
has caused the Debian Bug report #1006981,
regarding rails: flaky autopkgtest on some ci.d.n architectures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1006981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006981
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web