Input buildinfo: https://buildinfos.debian.net/buildinfo-pool/r/ruby-sidekiq-cron/ruby-sidekiq-cron_1.2.0-1_all.buildinfo Use metasnap for getting required timestamps New buildinfo file: /tmp/ruby-sidekiq-cron-1.2.0-1nac54jdj/ruby-sidekiq-cron_1.2.0-1_all.buildinfo Get source package info: ruby-sidekiq-cron=1.2.0-1 Source URL: http://snapshot.notset.fr/mr/package/ruby-sidekiq-cron/1.2.0-1/srcfiles?fileinfo=1 env -i PATH=/usr/sbin:/usr/bin:/sbin:/bin TMPDIR=/tmp mmdebstrap --arch=amd64 --include=adduser=3.118 autoconf=2.69-14 automake=1:1.16.3-2 autopoint=0.21-4 autotools-dev=20180224.1+nmu1 base-files=11.1 base-passwd=3.5.50 bash=5.1-3 binutils=2.35.2-2 binutils-common=2.35.2-2 binutils-x86-64-linux-gnu=2.35.2-2 bsdextrautils=2.36.1-7 bsdutils=1:2.36.1-7 build-essential=12.9 bzip2=1.0.8-4 ca-certificates=20210119 coreutils=8.32-4+b1 cpp=4:10.2.1-1 cpp-10=10.2.1-6 dash=0.5.11+git20210120+802ebd4-1 debconf=1.5.77 debhelper=13.3.4 debianutils=4.11.2 devscripts=2.21.2 dh-autoreconf=20 dh-strip-nondeterminism=1.12.0-1 diffutils=1:3.7-5 dirmngr=2.2.27-2 dpkg=1.20.9 dpkg-dev=1.20.9 dwz=0.14-1 fakeroot=1.25.3-1.1 file=1:5.39-3 findutils=4.8.0-1 fonts-glyphicons-halflings=1.009~3.4.1+dfsg-2 g++=4:10.2.1-1 g++-10=10.2.1-6 gcc=4:10.2.1-1 gcc-10=10.2.1-6 gcc-10-base=10.2.1-6 gem2deb=1.4 gem2deb-test-runner=1.4 gettext=0.21-4 gettext-base=0.21-4 gnupg=2.2.27-2 gnupg-l10n=2.2.27-2 gnupg-utils=2.2.27-2 gpg=2.2.27-2 gpg-agent=2.2.27-2 gpg-wks-client=2.2.27-2 gpg-wks-server=2.2.27-2 gpgconf=2.2.27-2 gpgsm=2.2.27-2 gpgv=2.2.27-2 grep=3.6-1 groff-base=1.22.4-6 gzip=1.10-4 hostname=3.23 init-system-helpers=1.60 intltool-debian=0.35.0+20060710.5 libacl1=2.2.53-10 libarchive-zip-perl=1.68-1 libasan6=10.2.1-6 libassuan0=2.5.4-1 libatomic1=10.2.1-6 libattr1=1:2.4.48-6 libaudit-common=1:3.0-2 libaudit1=1:3.0-2 libb-hooks-op-check-perl=0.22-1+b3 libbinutils=2.35.2-2 libblkid1=2.36.1-7 libbsd0=0.11.3-1 libbz2-1.0=1.0.8-4 libc-bin=2.31-12 libc-dev-bin=2.31-12 libc6=2.31-12 libc6-dev=2.31-12 libcap-ng0=0.7.9-2.2+b1 libcc1-0=10.2.1-6 libclass-method-modifiers-perl=2.13-1 libcom-err2=1.46.2-2 libcrypt-dev=1:4.4.18-4 libcrypt1=1:4.4.18-4 libctf-nobfd0=2.35.2-2 libctf0=2.35.2-2 libdb5.3=5.3.28+dfsg1-0.8 libdebconfclient0=0.259 libdebhelper-perl=13.3.4 libdevel-callchecker-perl=0.008-1+b2 libdpkg-perl=1.20.9 libdynaloader-functions-perl=0.003-1.1 libedit2=3.1-20191231-2+b1 libelf1=0.183-3 libencode-locale-perl=1.05-1.1 libexpat1=2.2.10-2 libfakeroot=1.25.3-1.1 libffi7=3.3-6 libfile-dirlist-perl=0.05-2 libfile-homedir-perl=1.006-1 libfile-listing-perl=6.14-1 libfile-stripnondeterminism-perl=1.12.0-1 libfile-touch-perl=0.11-1 libfile-which-perl=1.23-1 libgcc-10-dev=10.2.1-6 libgcc-s1=10.2.1-6 libgcrypt20=1.8.7-6 libgdbm-compat4=1.19-2 libgdbm6=1.19-2 libgmp-dev=2:6.2.1+dfsg-1 libgmp10=2:6.2.1+dfsg-1 libgmpxx4ldbl=2:6.2.1+dfsg-1 libgnutls30=3.7.1-5 libgomp1=10.2.1-6 libgpg-error0=1.38-2 libgssapi-krb5-2=1.18.3-5 libhogweed6=3.7.3-1 libhtml-parser-perl=3.76-1 libhtml-tagset-perl=3.20-4 libhtml-tree-perl=5.07-2 libhttp-cookies-perl=6.10-1 libhttp-date-perl=6.05-1 libhttp-message-perl=6.29-1 libhttp-negotiate-perl=6.01-1 libicu67=67.1-6 libidn2-0=2.3.0-5 libimport-into-perl=1.002005-1 libio-html-perl=1.004-2 libio-pty-perl=1:1.15-2 libio-socket-ssl-perl=2.069-1 libipc-run-perl=20200505.0-1 libisl23=0.23-1 libitm1=10.2.1-6 libjemalloc2=5.2.1-3 libjs-bootstrap=3.4.1+dfsg-2 libk5crypto3=1.18.3-5 libkeyutils1=1.6.1-2 libkrb5-3=1.18.3-5 libkrb5support0=1.18.3-5 libksba8=1.5.0-3 libldap-2.4-2=2.4.57+dfsg-3 liblsan0=10.2.1-6 liblua5.1-0=5.1.5-8.1+b3 liblwp-mediatypes-perl=6.04-1 liblwp-protocol-https-perl=6.10-1 liblz4-1=1.9.3-2 liblzf1=3.6-3 liblzma5=5.2.5-2 libmagic-mgc=1:5.39-3 libmagic1=1:5.39-3 libmd0=1.0.3-3 libmodule-runtime-perl=0.016-1 libmoo-perl=2.004004-1 libmount1=2.36.1-7 libmpc3=1.2.0-1 libmpdec3=2.5.1-2 libmpfr6=4.1.0-3 libncursesw6=6.2+20201114-2 libnet-http-perl=6.20-1 libnet-ssleay-perl=1.88-3+b1 libnettle8=3.7.3-1 libnpth0=1.6-3 libnsl-dev=1.3.0-2 libnsl2=1.3.0-2 libp11-kit0=0.23.22-1 libpam-modules=1.4.0-7 libpam-modules-bin=1.4.0-7 libpam-runtime=1.4.0-7 libpam0g=1.4.0-7 libparams-classify-perl=0.015-1+b3 libpcre2-8-0=10.36-2 libpcre3=2:8.39-13 libperl5.32=5.32.1-4 libpipeline1=1.5.3-1 libpython3-stdlib=3.9.2-3 libpython3.9-minimal=3.9.2-1 libpython3.9-stdlib=3.9.2-1 libquadmath0=10.2.1-6 libreadline8=8.1-2 librole-tiny-perl=2.002004-1 libruby2.7=2.7.3-2 libsasl2-2=2.1.27+dfsg-2.1 libsasl2-modules-db=2.1.27+dfsg-2.1 libseccomp2=2.5.1-1 libselinux1=3.1-3 libsemanage-common=3.1-1 libsemanage1=3.1-1+b2 libsepol1=3.1-1 libsigsegv2=2.13-1 libsmartcols1=2.36.1-7 libsqlite3-0=3.34.1-3 libssl1.1=1.1.1k-1 libstdc++-10-dev=10.2.1-6 libstdc++6=10.2.1-6 libstrictures-perl=2.000006-1 libsub-override-perl=0.09-2 libsub-quote-perl=2.006006-1 libsystemd0=247.3-5 libtasn1-6=4.16.0-2 libtimedate-perl=2.3300-2 libtinfo6=6.2+20201114-2 libtirpc-common=1.3.1-1 libtirpc-dev=1.3.1-1 libtirpc3=1.3.1-1 libtool=2.4.6-15 libtry-tiny-perl=0.30-1 libtsan0=10.2.1-6 libubsan1=10.2.1-6 libuchardet0=0.0.7-1 libudev1=247.3-5 libunistring2=0.9.10-4 liburi-perl=5.08-1 libuuid1=2.36.1-7 libwww-perl=6.53-1 libwww-robotrules-perl=6.02-1 libxml2=2.9.10+dfsg-6.7 libyaml-0-2=0.2.2-1 libzstd1=1.4.8+dfsg-2.1 linux-libc-dev=5.10.40-1 login=1:4.8.1-1 lsb-base=11.1.0 lua-bitop=1.0.2-5 lua-cjson=2.1.0+dfsg-2.1 m4=1.4.18-5 make=4.3-4.1 man-db=2.9.4-2 mawk=1.3.4.20200120-2 media-types=4.0.0 ncurses-base=6.2+20201114-2 ncurses-bin=6.2+20201114-2 netbase=6.3 openssl=1.1.1k-1 passwd=1:4.8.1-1 patch=2.7.6-7 patchutils=0.4.2-1 perl=5.32.1-4 perl-base=5.32.1-4 perl-modules-5.32=5.32.1-4 perl-openssl-defaults=5 pinentry-curses=1.1.0-4 po-debconf=1.0.21+nmu1 python3=3.9.2-3 python3-minimal=3.9.2-3 python3.9=3.9.2-1 python3.9-minimal=3.9.2-1 rake=13.0.3-1 readline-common=8.1-2 redis-server=5:6.0.14-1 redis-tools=5:6.0.14-1 ruby=1:2.7+2 ruby-all-dev=1:2.7+2 ruby-atomic=1.1.16-3+b1 ruby-celluloid=0.16.0-5 ruby-concurrent=1.1.6+dfsg-3 ruby-connection-pool=2.2.2-1 ruby-et-orbi=1.2.2-1 ruby-fugit=1.3.8-1 ruby-hitimes=1.2.1-4 ruby-metaclass=0.0.4-1.1 ruby-minitest=5.13.0-1 ruby-mocha=1.7.0-1 ruby-mustermann=1.1.1-1 ruby-net-telnet=0.1.1-2 ruby-power-assert=1.1.7-2 ruby-raabro=1.3.1-1 ruby-rack=2.1.4-3 ruby-rack-protection=2.0.8.1-2 ruby-rack-test=0.7.0-1.1 ruby-redis=4.2.5-1 ruby-redis-namespace=1.7.0-1 ruby-ruby2-keywords=0.0.2-2 ruby-rubygems=3.2.5-2 ruby-shoulda-context=2.0.0-2 ruby-sidekiq=6.0.4+dfsg-2 ruby-sinatra=2.0.8.1-2 ruby-test-unit=3.3.9-1 ruby-thread-safe=0.3.6-1 ruby-tilt=2.0.10-1 ruby-timers=4.1.1-2.1 ruby-tzinfo=1.2.6-1 ruby-xmlrpc=0.3.0-2 ruby2.7=2.7.3-2 ruby2.7-dev=2.7.3-2 rubygems-integration=1.18 sed=4.7-1 sensible-utils=0.0.14 sysvinit-utils=2.96-7 tar=1.34+dfsg-1 tzdata=2021a-1 util-linux=2.36.1-7 wdiff=1.2.2-2+b1 xz-utils=5.2.5-2 zlib1g=1:1.2.11.dfsg-2 --variant=apt --aptopt=Acquire::Check-Valid-Until "false" --aptopt=Acquire::http::Dl-Limit "1000"; --aptopt=Acquire::https::Dl-Limit "1000"; --aptopt=Acquire::Retries "5"; --aptopt=APT::Get::allow-downgrades "true"; --keyring=/usr/share/keyrings/ --essential-hook=chroot "$1" sh -c "apt-get --yes install fakeroot util-linux" --essential-hook=copy-in /usr/share/keyrings/debian-archive-bullseye-automatic.gpg /usr/share/keyrings/debian-archive-bullseye-security-automatic.gpg /usr/share/keyrings/debian-archive-bullseye-stable.gpg /usr/share/keyrings/debian-archive-buster-automatic.gpg /usr/share/keyrings/debian-archive-buster-security-automatic.gpg /usr/share/keyrings/debian-archive-buster-stable.gpg /usr/share/keyrings/debian-archive-keyring.gpg /usr/share/keyrings/debian-archive-removed-keys.gpg /usr/share/keyrings/debian-archive-stretch-automatic.gpg /usr/share/keyrings/debian-archive-stretch-security-automatic.gpg /usr/share/keyrings/debian-archive-stretch-stable.gpg /usr/share/keyrings/debian-ports-archive-keyring-removed.gpg /usr/share/keyrings/debian-ports-archive-keyring.gpg /usr/share/keyrings/debian-keyring.gpg /etc/apt/trusted.gpg.d/ --essential-hook=chroot "$1" sh -c "rm /etc/apt/sources.list && echo 'deb http://snapshot.notset.fr/archive/debian/20210814T212851Z/ bookworm main deb-src http://snapshot.notset.fr/archive/debian/20210814T212851Z/ bookworm main deb http://snapshot.notset.fr/archive/debian/20210624T142826Z/ unstable main' >> /etc/apt/sources.list && apt-get update" --customize-hook=chroot "$1" useradd --no-create-home -d /nonexistent -p "" builduser -s /bin/bash --customize-hook=chroot "$1" env sh -c "apt-get source --only-source -d ruby-sidekiq-cron=1.2.0-1 && mkdir -p /build/ruby-sidekiq-cron-ZvQUJI && dpkg-source --no-check -x /*.dsc /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0 && chown -R builduser:builduser /build/ruby-sidekiq-cron-ZvQUJI" --customize-hook=chroot "$1" env --unset=TMPDIR runuser builduser -c "cd /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0 && env DEB_BUILD_OPTIONS="parallel=4" LANG="C.UTF-8" LC_ALL="C.UTF-8" SOURCE_DATE_EPOCH="1623780694" dpkg-buildpackage -uc -a amd64 --build=all" --customize-hook=sync-out /build/ruby-sidekiq-cron-ZvQUJI /tmp/ruby-sidekiq-cron-1.2.0-1nac54jdj bullseye /dev/null deb http://snapshot.notset.fr/archive/debian/20210624T142826Z unstable main I: automatically chosen mode: root I: chroot architecture amd64 is equal to the host's architecture I: automatically chosen format: tar I: using /tmp/mmdebstrap.OiiYb_lOUf as tempdir I: running apt-get update... I: downloading packages with apt... I: extracting archives... I: installing essential packages... I: running --essential-hook in shell: sh -c 'chroot "$1" sh -c "apt-get --yes install fakeroot util-linux"' exec /tmp/mmdebstrap.OiiYb_lOUf Reading package lists... Building dependency tree... util-linux is already the newest version (2.36.1-7). The following NEW packages will be installed: fakeroot libfakeroot 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 134 kB of archives. After this operation, 397 kB of additional disk space will be used. Get:1 http://snapshot.notset.fr/archive/debian/20210624T142826Z unstable/main amd64 libfakeroot amd64 1.25.3-1.1 [47.0 kB] Get:2 http://snapshot.notset.fr/archive/debian/20210624T142826Z unstable/main amd64 fakeroot amd64 1.25.3-1.1 [87.0 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 134 kB in 0s (1087 kB/s) Selecting previously unselected package libfakeroot:amd64. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 4667 files and directories currently installed.) Preparing to unpack .../libfakeroot_1.25.3-1.1_amd64.deb ... Unpacking libfakeroot:amd64 (1.25.3-1.1) ... Selecting previously unselected package fakeroot. Preparing to unpack .../fakeroot_1.25.3-1.1_amd64.deb ... Unpacking fakeroot (1.25.3-1.1) ... Setting up libfakeroot:amd64 (1.25.3-1.1) ... Setting up fakeroot (1.25.3-1.1) ... update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode Processing triggers for libc-bin (2.31-12) ... I: running special hook: copy-in /usr/share/keyrings/debian-archive-bullseye-automatic.gpg /usr/share/keyrings/debian-archive-bullseye-security-automatic.gpg /usr/share/keyrings/debian-archive-bullseye-stable.gpg /usr/share/keyrings/debian-archive-buster-automatic.gpg /usr/share/keyrings/debian-archive-buster-security-automatic.gpg /usr/share/keyrings/debian-archive-buster-stable.gpg /usr/share/keyrings/debian-archive-keyring.gpg /usr/share/keyrings/debian-archive-removed-keys.gpg /usr/share/keyrings/debian-archive-stretch-automatic.gpg /usr/share/keyrings/debian-archive-stretch-security-automatic.gpg /usr/share/keyrings/debian-archive-stretch-stable.gpg /usr/share/keyrings/debian-ports-archive-keyring-removed.gpg /usr/share/keyrings/debian-ports-archive-keyring.gpg /usr/share/keyrings/debian-keyring.gpg /etc/apt/trusted.gpg.d/ I: running --essential-hook in shell: sh -c 'chroot "$1" sh -c "rm /etc/apt/sources.list && echo 'deb http://snapshot.notset.fr/archive/debian/20210814T212851Z/ bookworm main deb-src http://snapshot.notset.fr/archive/debian/20210814T212851Z/ bookworm main deb http://snapshot.notset.fr/archive/debian/20210624T142826Z/ unstable main' >> /etc/apt/sources.list && apt-get update"' exec /tmp/mmdebstrap.OiiYb_lOUf Get:1 http://snapshot.notset.fr/archive/debian/20210814T212851Z bookworm InRelease [81.6 kB] Hit:2 http://snapshot.notset.fr/archive/debian/20210624T142826Z unstable InRelease Ign:3 http://snapshot.notset.fr/archive/debian/20210814T212851Z bookworm/main Sources Ign:4 http://snapshot.notset.fr/archive/debian/20210814T212851Z bookworm/main amd64 Packages Ign:3 http://snapshot.notset.fr/archive/debian/20210814T212851Z bookworm/main Sources Ign:4 http://snapshot.notset.fr/archive/debian/20210814T212851Z bookworm/main amd64 Packages Ign:3 http://snapshot.notset.fr/archive/debian/20210814T212851Z bookworm/main Sources Ign:4 http://snapshot.notset.fr/archive/debian/20210814T212851Z bookworm/main amd64 Packages Get:3 http://snapshot.notset.fr/archive/debian/20210814T212851Z bookworm/main Sources [11.4 MB] Get:4 http://snapshot.notset.fr/archive/debian/20210814T212851Z bookworm/main amd64 Packages [11.1 MB] Fetched 22.6 MB in 20s (1156 kB/s) Reading package lists... I: installing remaining packages inside the chroot... I: running --customize-hook in shell: sh -c 'chroot "$1" useradd --no-create-home -d /nonexistent -p "" builduser -s /bin/bash' exec /tmp/mmdebstrap.OiiYb_lOUf I: running --customize-hook in shell: sh -c 'chroot "$1" env sh -c "apt-get source --only-source -d ruby-sidekiq-cron=1.2.0-1 && mkdir -p /build/ruby-sidekiq-cron-ZvQUJI && dpkg-source --no-check -x /*.dsc /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0 && chown -R builduser:builduser /build/ruby-sidekiq-cron-ZvQUJI"' exec /tmp/mmdebstrap.OiiYb_lOUf Reading package lists... NOTICE: 'ruby-sidekiq-cron' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/ruby-team/ruby-sidekiq-cron.git Please use: git clone https://salsa.debian.org/ruby-team/ruby-sidekiq-cron.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 184 kB of source archives. Get:1 http://snapshot.notset.fr/archive/debian/20210814T212851Z bookworm/main ruby-sidekiq-cron 1.2.0-1 (dsc) [2235 B] Get:2 http://snapshot.notset.fr/archive/debian/20210814T212851Z bookworm/main ruby-sidekiq-cron 1.2.0-1 (tar) [177 kB] Get:3 http://snapshot.notset.fr/archive/debian/20210814T212851Z bookworm/main ruby-sidekiq-cron 1.2.0-1 (diff) [4332 B] Fetched 184 kB in 0s (996 kB/s) Download complete and in download only mode W: Download is performed unsandboxed as root as file 'ruby-sidekiq-cron_1.2.0-1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) dpkg-source: info: extracting ruby-sidekiq-cron in /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0 dpkg-source: info: unpacking ruby-sidekiq-cron_1.2.0.orig.tar.gz dpkg-source: info: unpacking ruby-sidekiq-cron_1.2.0-1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying remove-rubygems-bundler.patch dpkg-source: info: applying disable-randomly-failing-tests.patch I: running --customize-hook in shell: sh -c 'chroot "$1" env --unset=TMPDIR runuser builduser -c "cd /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0 && env DEB_BUILD_OPTIONS="parallel=4" LANG="C.UTF-8" LC_ALL="C.UTF-8" SOURCE_DATE_EPOCH="1623780694" dpkg-buildpackage -uc -a amd64 --build=all"' exec /tmp/mmdebstrap.OiiYb_lOUf dpkg-buildpackage: info: source package ruby-sidekiq-cron dpkg-buildpackage: info: source version 1.2.0-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Pirate Praveen dpkg-source --before-build . fakeroot debian/rules clean dh clean --buildsystem=ruby --with ruby dh_auto_clean -O--buildsystem=ruby dh_ruby --clean dh_ruby --clean dh_autoreconf_clean -O--buildsystem=ruby dh_clean -O--buildsystem=ruby debian/rules build-indep dh build-indep --buildsystem=ruby --with ruby dh_update_autotools_config -i -O--buildsystem=ruby dh_autoreconf -i -O--buildsystem=ruby dh_auto_configure -i -O--buildsystem=ruby dh_ruby --configure dh_auto_build -i -O--buildsystem=ruby dh_ruby --build dh_ruby --build dh_auto_test -i -O--buildsystem=ruby dh_ruby --test create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary-indep dh binary-indep --buildsystem=ruby --with ruby dh_testroot -i -O--buildsystem=ruby dh_prep -i -O--buildsystem=ruby dh_auto_install -i -O--buildsystem=ruby dh_ruby --install /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron dh_ruby --install ┌──────────────────────────────────────────────────────────────────────────────┐ │ Install files │ └──────────────────────────────────────────────────────────────────────────────┘ install -d /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron.rb /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron.rb install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/web.rb /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/web.rb install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/views/cron.erb /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/views/cron.erb install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/views/cron_show.slim /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/views/cron_show.slim install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/views/cron.slim /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/views/cron.slim install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/views/cron_show.erb /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/views/cron_show.erb install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/support.rb /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/support.rb install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/poller.rb /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/poller.rb install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/launcher.rb /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/launcher.rb install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/job.rb install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/web_extension.rb /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/web_extension.rb install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/locales/de.yml /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/locales/de.yml install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/locales/ru.yml /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/locales/ru.yml install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/locales/ja.yml /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/locales/ja.yml install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/locales/en.yml /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/locales/en.yml install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/locales/zh-CN.yml /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq/cron/locales/zh-CN.yml install -D -m644 /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq-cron.rb /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby/sidekiq-cron.rb ┌──────────────────────────────────────────────────────────────────────────────┐ │ Install Rubygems integration metadata │ └──────────────────────────────────────────────────────────────────────────────┘ generating gemspec at /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/share/rubygems-integration/all/specifications/sidekiq-cron-1.2.0.gemspec /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner ┌──────────────────────────────────────────────────────────────────────────────┐ │ Checking Rubygems dependency resolution on ruby2.7 │ └──────────────────────────────────────────────────────────────────────────────┘ GEM_PATH=/build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/share/rubygems-integration/all:/build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 ruby2.7 -e gem\ \"sidekiq-cron\" ┌──────────────────────────────────────────────────────────────────────────────┐ │ Run tests for ruby2.7 from debian/ruby-tests.rake │ └──────────────────────────────────────────────────────────────────────────────┘ RUBYLIB=/build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby:. GEM_PATH=/build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-sidekiq-cron/usr/share/rubygems-integration/all:/build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 ruby2.7 -S rake -f debian/ruby-tests.rake ./debian/start-redis-server.sh ruby2.7 -S rake -f /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-tests.rake test + PID=1164512 + trap cleanup INT EXIT TERM ALRM + ruby2.7 -S rake -f /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/debian/ruby-tests.rake test + redis-server 1164512:C 11 Oct 2021 01:37:13.350 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1164512:C 11 Oct 2021 01:37:13.350 # Redis version=6.0.14, bits=64, commit=00000000, modified=0, pid=1164512, just started 1164512:C 11 Oct 2021 01:37:13.350 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf 1164512:M 11 Oct 2021 01:37:13.352 * Increased maximum number of open files to 10032 (it was originally set to 1024). 1164512:M 11 Oct 2021 01:37:13.353 * Running mode=standalone, port=6379. 1164512:M 11 Oct 2021 01:37:13.353 # Server initialized 1164512:M 11 Oct 2021 01:37:13.353 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. 1164512:M 11 Oct 2021 01:37:13.353 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo madvise > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled (set to 'madvise' or 'never'). 1164512:M 11 Oct 2021 01:37:13.354 * Ready to accept connections /usr/bin/ruby2.7 -w -I"lib:test" /usr/share/rubygems-integration/all/gems/rake-13.0.3/lib/rake/rake_test_loader.rb "test/unit/job_test.rb" /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/test/test_helper.rb:50: warning: `*' interpreted as argument prefix /usr/share/rubygems-integration/all/gems/sidekiq-6.0.4/lib/sidekiq/logger.rb:108: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /usr/lib/ruby/2.7.0/logger.rb:379: warning: The called method `initialize' is defined here /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:308: warning: assigned but unused variable - e /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85: warning: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85: warning: loading in progress, circular require considered harmful - /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron.rb from /usr/share/rubygems-integration/all/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in `
' from /usr/share/rubygems-integration/all/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in `select' from /usr/share/rubygems-integration/all/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:17:in `block in
' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' from /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/test/unit/job_test.rb:2:in `' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' from /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/test/test_helper.rb:26:in `' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' from /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq-cron.rb:2:in `' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' from /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron.rb:2:in `' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' from /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/poller.rb:3:in `' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized Run options: --seed 32408 # Running: S/build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized S/build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/test/test_helper.rb:58: warning: instance variable @queue_name_prefix not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:127: warning: instance variable @description not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ......./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') .`Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ....../build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ../build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ../build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') .../build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:127: warning: instance variable @description not initialized .........../build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') .....S/build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ...`Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/lib/ruby/vendor_ruby/redis/namespace.rb:469:in `call_with_namespace') ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized ./build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:99: warning: instance variable @queue not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:396: warning: instance variable @description not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized /build/ruby-sidekiq-cron-ZvQUJI/ruby-sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:398: warning: instance variable @message not initialized .. Finished in 0.490209s, 173.3953 runs/s, 340.6707 assertions/s. 85 runs, 167 assertions, 0 failures, 0 errors, 3 skips You have skipped tests. Run with --verbose for details. + cleanup + kill -9 1164512 ┌──────────────────────────────────────────────────────────────────────────────┐ │ dh_ruby --install finished │ └──────────────────────────────────────────────────────────────────────────────┘ dh_installdocs -i -O--buildsystem=ruby dh_ruby_fixdocs -i -O--buildsystem=ruby dh_installchangelogs -i -O--buildsystem=ruby dh_installexamples -i -O--buildsystem=ruby dh_installsystemduser -i -O--buildsystem=ruby dh_perl -i -O--buildsystem=ruby dh_link -i -O--buildsystem=ruby dh_strip_nondeterminism -i -O--buildsystem=ruby dh_compress -X.rb -i -O--buildsystem=ruby dh_fixperms -i -O--buildsystem=ruby dh_missing -i -O--buildsystem=ruby dh_ruby_fixdepends -i -O--buildsystem=ruby dh_installdeb -i -O--buildsystem=ruby dh_gencontrol -i -O--buildsystem=ruby dpkg-gencontrol: warning: Depends field of package ruby-sidekiq-cron: substitution variable ${shlibs:Depends} used, but is not defined dpkg-gencontrol: warning: package ruby-sidekiq-cron: substitution variable ${ruby:Depends} unused, but is defined dh_md5sums -i -O--buildsystem=ruby dh_builddeb -i -O--buildsystem=ruby dpkg-deb: building package 'ruby-sidekiq-cron' in '../ruby-sidekiq-cron_1.2.0-1_all.deb'. dpkg-genbuildinfo --build=all dpkg-genchanges --build=all >../ruby-sidekiq-cron_1.2.0-1_all.changes dpkg-genchanges: info: binary-only arch-indep upload (source code and arch-specific packages not included) dpkg-source --after-build . dpkg-buildpackage: info: binary-only upload (no source included) I: running special hook: sync-out /build/ruby-sidekiq-cron-ZvQUJI /tmp/ruby-sidekiq-cron-1.2.0-1nac54jdj I: cleaning package lists and apt cache... I: creating tarball... I: done I: removing tempdir /tmp/mmdebstrap.OiiYb_lOUf... I: success in 371.5812 seconds md5: ruby-sidekiq-cron_1.2.0-1_all.deb: OK sha1: ruby-sidekiq-cron_1.2.0-1_all.deb: OK sha256: ruby-sidekiq-cron_1.2.0-1_all.deb: OK Checksums: OK