[Octave-bug-tracker] [bug #52850] unused parameter warning during build

[Rik]

Follow-up Comment #2, bug #52850 (project octave):

Is there something to change in the buildbot configuration so that we are
properly capturing stderr during the compile stage?

I went back and looked at a compile log from an earlier buildbot session and
the warnings are there.  See
http://buildbot.octave.org:8010/builders/no-extras-debian/builds/1265/steps/compile/logs/stdio

Or is it that the compile warnings are being delivered to stdout and we
actually need a post-compile script to grep for "warning:" in the stdout log?

Changing the regexp used might help with some of the test logs as well which
often show warnings, but that is simply the use of the warning statement in
the code.  For example, from this log:
http://buildbot.octave.org:8010/builders/clang-osx/builds/858/steps/test/logs/warnings%20%287%29


 saved_opts = warning ();
 warning ("off", "all");
 warning (saved_opts);
 warning ("off", "ode15s:mass_state_dependent_provided", "local");
 warning ("off", "ode15s:mass_state_dependent_provided", "local");
 warning ("off", "ode15s:mass_state_dependent_provided", "local");
 warning ("off", "ode15s:mass_state_dependent_provided", "local");


If the regexp were changed to "warning:" then these would not appear.  But any
real warning would since those are prefaced with "warning:".



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?52850>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/