[DRE-maint] Bug#841574: atig: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: db.execute "VACUUM status"

[Lucas Nussbaum]

Source: atig
Version: 0.6.1-1
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>      Failure/Error: db.execute "VACUUM status"
> 
>      SQLite3::SQLException:
>        unknown database status
>      # ./lib/atig/db/statuses.rb:126:in `block in cleanup'
>      # ./lib/atig/db/sql.rb:27:in `execute'
>      # ./lib/atig/db/statuses.rb:121:in `cleanup'
>      # ./spec/db/statuses_spec.rb:180:in `block (2 levels) in <top (required)>'
> 
> Top 10 slowest examples (11.24 seconds, 90.5% of total time):
>   Atig::Db::Statuses should cleanup
>     10.39 seconds ./spec/db/statuses_spec.rb:174
>   Atig::Db::Statuses should call listeners
>     0.10167 seconds ./spec/db/statuses_spec.rb:41
>   Atig::Db::Statuses should have uniq tid/sid when removed
>     0.10135 seconds ./spec/db/statuses_spec.rb:164
>   Atig::Db::Statuses should have unique tid
>     0.09696 seconds ./spec/db/statuses_spec.rb:73
>   Atig::Db::Statuses should remove by id
>     0.09585 seconds ./spec/db/statuses_spec.rb:159
>   Atig::Db::Statuses should be found by tid
>     0.09113 seconds ./spec/db/statuses_spec.rb:104
>   Atig::Db::Statuses should be found by screen_name
>     0.09076 seconds ./spec/db/statuses_spec.rb:132
>   Atig::Db::Statuses should be re-openable
>     0.08963 seconds ./spec/db/statuses_spec.rb:37
>   Atig::Db::Statuses should be found by screen_name with limit
>     0.08954 seconds ./spec/db/statuses_spec.rb:148
>   Atig::Db::Statuses should not contain duplicate
>     0.08811 seconds ./spec/db/statuses_spec.rb:56
> 
> Top 10 slowest example groups:
>   Atig::Db::Statuses
>     0.77699 seconds average (11.65 seconds / 15 examples) ./spec/db/statuses_spec.rb:6
>   Atig::Db::Lists
>     0.03209 seconds average (0.32088 seconds / 10 examples) ./spec/db/lists_spec.rb:5
>   Atig::Db::Followings when it is empty
>     0.0305 seconds average (0.0305 seconds / 1 example) ./spec/db/followings_spec.rb:5
>   Atig::Db::Followings when updated users
>     0.02754 seconds average (0.27539 seconds / 10 examples) ./spec/db/followings_spec.rb:20
>   Atig::Command::Autofix
>     0.00496 seconds average (0.00991 seconds / 2 examples) ./spec/command/autofix_spec.rb:5
>   Atig::Command::Whois
>     0.00195 seconds average (0.00586 seconds / 3 examples) ./spec/command/whois_spec.rb:8
>   Atig::Command::Destroy when remove recently tweet
>     0.00188 seconds average (0.00565 seconds / 3 examples) ./spec/command/destroy_spec.rb:21
>   Atig::Command::Favorite
>     0.00183 seconds average (0.00916 seconds / 5 examples) ./spec/command/favorite_spec.rb:5
>   Atig::Command::Thread
>     0.00175 seconds average (0.01222 seconds / 7 examples) ./spec/command/thread_spec.rb:5
>   Atig::Command::Option when have bool property
>     0.0015 seconds average (0.003 seconds / 2 examples) ./spec/command/option_spec.rb:44
> 
> Finished in 12.41 seconds (files took 0.50439 seconds to load)
> 182 examples, 1 failure
> 
> Failed examples:
> 
> rspec ./spec/db/statuses_spec.rb:174 # Atig::Db::Statuses should cleanup
> 
> [Coveralls] Outside the Travis environment, not sending data.
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby2.3" failed: 

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/atig_0.6.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.