Weaken test to improve flakiness

[MichaelChirico]

Closes #212 by reducing flakiness to ~.1%

[aadler]

Maybe drop the tolerance back to 2e-2 again, given that four platforms are failing?

[MichaelChirico]

Hmm those errors look unrelated; I reproduce them on master:

  File ‘nloptr/libs/nloptr.so’:
    Found ‘_ZSt4cerr’, possibly from ‘std::cerr’ (C++)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘_ZSt4cout’, possibly from ‘std::cout’ (C++)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘__printf_chk’, possibly from ‘printf’ (C)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘abort’, possibly from ‘abort’ (C)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘exit’, possibly from ‘exit’ (C)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘putchar’, possibly from ‘putchar’ (C)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘puts’, possibly from ‘printf’ (C), ‘puts’ (C)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘stderr’, possibly from ‘stderr’ (C)
      Object: ‘nlopt/lib/libnlopt.a’
  
  Compiled code should not call entry points which might terminate R nor
  write to stdout/stderr instead of to the console, nor use Fortran I/O
  nor system RNGs nor [v]sprintf.
  
  See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.

[aadler]

Hmm those errors look unrelated, are they present on master?

  File ‘nloptr/libs/nloptr.so’:
    Found ‘_ZSt4cerr’, possibly from ‘std::cerr’ (C++)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘_ZSt4cout’, possibly from ‘std::cout’ (C++)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘__printf_chk’, possibly from ‘printf’ (C)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘abort’, possibly from ‘abort’ (C)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘exit’, possibly from ‘exit’ (C)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘putchar’, possibly from ‘putchar’ (C)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘puts’, possibly from ‘printf’ (C), ‘puts’ (C)
      Object: ‘nlopt/lib/libnlopt.a’
    Found ‘stderr’, possibly from ‘stderr’ (C)
      Object: ‘nlopt/lib/libnlopt.a’
  
  Compiled code should not call entry points which might terminate R nor
  write to stdout/stderr instead of to the console, nor use Fortran I/O
  nor system RNGs nor [v]sprintf.
  
  See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.

I think those may be the issues with which @astamm is dealing with the nlopt sources themselves.

[astamm]

Yes. I have a PR under review here: stevengj/nlopt#608.
Once merged, I am planning to move towards a bundling strategy as in: https://github.com/astamm/nloptrbundled, which takes care of these warnings.