autopkgtest failure on armhf due to stderr output

[Graham Inggs]

Autopkgtests fail on armhf only due to output similar to the following on stderr:

/usr/include/c++/9/bits/stl_algobase.h:438:5: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<const long long int*, std::vector<long long int> >’ changed in GCC 7.1
  438 | __copy_move_a2(_II __first, _II __last, _OI __result)
      | ^~~~~~~~~~~~~~
/usr/include/c++/9/bits/stl_algobase.h:438:5: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<const long long int*, std::vector<long long int> >’ changed in GCC 7.1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77728

https://wiki.ubuntu.com/GCC7

[Graham Inggs (ginggs)]

# ignore GCC 7.1 notes on armhf
force-badtest ciftilib/1.5.3-3/armhf
force-badtest mathic/1.0~git20181123-1/armhf
force-badtest primesieve/7.5+ds-3/armhf

Keeping this bug open with the update-excuse tag should cause it to show up on update_excuses if an update is required.

[Graham Inggs (ginggs)]

# ignore GCC 7.1 notes on armhf
force-reset-test ciftilib/1.5.3-3/armhf
force-reset-test mathic/1.0~git20181123-1/armhf
force-reset-test primesieve/7.5+ds-3/armhf

[Steve Langasek (vorlon)]

I don't see why we would want a badtest here, which reduces CI coverage, rather than restoring the Ubuntu delta we previously had that sets Restrictions: allow-stderr.

[Graham Inggs (ginggs)]

force-reset-test here does reduce coverage on armhf, but allow-stderr would allow unexpected output on all other architectures.

[Graham Inggs (ginggs)]

I checked, and autopkgtest does not currently allow the following:

Restrictions: allow-stderr [armhf]

[Steve Langasek (vorlon)]

all of these autopkgtests now pass on armhf in focal and later.

[Graham Inggs (ginggs)]

All of these packages, except shark which was removed from unstable, are now in sync with Debian.