Description of problem: With patch https://review.gluster.org/21276 being merged, we should be passing the build without any warning on non-64bit arch too. To preserve the state, we need a build to FAIL if there are any warnings. Version-Release number of selected component (if applicable): master Expected results: A build with -m32 to run without any errors to pass the smoke. Additional info: When the job gets introduced, we can check for a week with 'skipped' vote, on failure, and then can make sure to PASS it for sometime, and then enable the vote, like we did for other jobs!
The easiest and most portable way is to build in mock for a 32-bit architecture. That prevents the need for having all 32-bit libraries, development tools and dependencies on the systems. This normally does quite nicely: mock -r fedora-rawhide-i386 rebuild <srcrpm> The https://build.gluster.org/job/strfmt_errors/ job uses such a configuration already.
What I currently do is run a mock build on 32-bit and grep it for specific warnings. What we want to do is run that with -Wall and we should be good. I'm going to assign this to sprint 5.
So, if we want the build to fail, shouldn't it be -Werror -Wall ? (and then, I think -Wall is not really "all", there is more warnings out there). using -Werror to detect failure also bring the question of "what when new warnings are added".
This is now done. There is a non-voting job that is failing. Please fix the warnings and file a new bug for a voting job.