Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693385 - request to change the version of fedora in fedora-smoke-job
Summary: request to change the version of fedora in fedora-smoke-job
Keywords:
Status: NEW
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-27 17:35 UTC by Amar Tumballi
Modified: 2019-03-28 15:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Amar Tumballi 2019-03-27 17:35:16 UTC
Description of problem:

There are at least 2 jobs which use 'fedora' while running smoke.

https://build.gluster.org/job/devrpm-fedora/ && https://build.gluster.org/job/fedora-smoke/

I guess we are running Fedora 28 in both of these, would be good to update it to higher version, say F29 (and soon F30).



Version-Release number of selected component (if applicable):
master



Additional info:
Would be good to remove '--enable-debug' in these builds on some jobs (there are 2 smoke, and 4 rpm build jobs). We should remove --enable-debug in at least 1 of these, so our release RPMs which has no DEBUG defined, can be warning free.

Comment 1 M. Scherer 2019-03-27 17:48:25 UTC
So, that requires to upgrade the builders (or reinstall them), I think it would be better to wait on F30 to do it only once.

Comment 2 Niels de Vos 2019-03-28 15:09:47 UTC
(In reply to Amar Tumballi from comment #0)
> Description of problem:
...
> Would be good to remove '--enable-debug' in these builds on some jobs (there
> are 2 smoke, and 4 rpm build jobs). We should remove --enable-debug in at
> least 1 of these, so our release RPMs which has no DEBUG defined, can be
> warning free.

I do not think these jobs are used for the RPMs that get marked as 'released' and land on download.gluster.org.

Comment 3 Amar Tumballi 2019-03-28 15:26:24 UTC
Agree, I was asking for a job without DEBUG mainly because a few times, there may be warning without DEBUG being there during compile (ref: https://review.gluster.org/22347 && https://review.gluster.org/22389 )

As I had --enable-debug while testing locally, never saw the warning, and none of the smoke tests captured the error. If we had a job without --enable-debug, we could have seen the warning while compiling, which would have failed Smoke.


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