Bug 1625489 - No need to run 'fedora-smoke' job on release branches (3.12/4.1)
Summary: No need to run 'fedora-smoke' job on release branches (3.12/4.1)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: 3.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-05 03:57 UTC by Amar Tumballi
Modified: 2018-09-05 10:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-05 10:44:15 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Amar Tumballi 2018-09-05 03:57:29 UTC 
Description of problem:
'fedora-smoke' job is to make sure we don't have any warnings on gcc8 (fedora28) when compiled. The fixes for it just landed in upstream master... and are not planned to be backported to release branches (for both 3.12/4.1), hence they are expected to fail. It makes sense to not to have this job run for release branches.

Version-Release number of selected component (if applicable):
3.12 / 4.1

How reproducible:
100%

Steps to Reproduce:
1. submit a patch to release branch.

Actual results:
fedora-smoke test fails.

Expected results:
No test at all (as it always fails)

Additional info:
Once release_5.0 branch is made, this job can run there, to preserve sanity, but not now.
Comment 1 Nigel Babu 2018-09-05 10:44:15 UTC 
Fixed in https://review.gluster.org/c/build-jobs/+/21088
Note You need to log in before you can comment on or make changes to this bug.