Bug 1887674 - Move cassandane tests to CI
Summary: Move cassandane tests to CI
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora
Classification: Fedora
Component: cyrus-imapd
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Zhukov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1856422
TreeView+ depends on / blocked
 
Reported: 2020-10-13 07:14 UTC by Pavel Zhukov
Modified: 2021-02-09 15:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Pavel Zhukov 2020-10-13 07:14:29 UTC
Description of problem:
Currently cassandane tests are called from %check section of spec file which is not the way they supposed to be used. 
This approach requires some hacks due to mock/koji limitation and it's broken from time to time due to either upstream changes [1] or fedora infra changes

Expected results:
Cassandane tests should be moved to separate package and use in CI system for  the purpose of gating


[1]
./testrunner.pl syntax OK
Base class package "Cyrus::Annotator::Daemon" is empty.
    (Perhaps you need to 'use' the module which defines that package first,
    or make that module available in @INC (@INC contains: /builddir/build/BUILDROOT/cyrus-imapd-3.2.3-2.fc34.x86_64/usr/share/perl5/vendor_perl /builddir/build/BUILDROOT/cyrus-imapd-3.2.3-2.fc34.x86_64/usr/lib64/perl5/vendor_perl /builddir/build/BUILDROOT/cyrus-imapd-3.2.3-2.fc34.x86_64/usr/share/perl5/5.32 /builddir/build/BUILDROOT/cyrus-imapd-3.2.3-2.fc34.x86_64/usr/lib64/perl5/5.32 /usr/local/lib64/perl5/5.32 /usr/local/share/perl5/5.32 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5).
 at ./utils/annotator.pl line 45.

Comment 1 Ben Cotton 2021-02-09 15:20:23 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.


Note You need to log in before you can comment on or make changes to this bug.