Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since July
2020. Can you please investigate the situation and fix it? I copied some
of the output at the bottom of this report. The test itself seems to
pass, but there's output on stderr, which without the allow-stderr
restriction is considered a failure by autopkgtest.

The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. [Release Team member hat on] Because
we're currently in the hard freeze for bookworm, I have marked this bug
as bookworm-ignore. Targeted fixes are still welcome.

More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html

https://ci.debian.net/data/autopkgtest/testing/amd64/p/polyml/32128171/log.gz

autopkgtest [19:23:44]: test upstream-polyc: [-----------------------
/usr/bin/ld: warning: /tmp/polyobj.2070.o: missing .note.GNU-stack
section implies executable stack
/usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a
future version of the linker
Test035.ML => Passed
Test162.ML => Passed

[...]

Test026.ML => Passed
autopkgtest [19:24:05]: test upstream-polyc: -----------------------]
autopkgtest [19:24:05]: test upstream-polyc:  - - - - - - - - - -
results - - - - - - - - - -
upstream-polyc       FAIL stderr: /usr/bin/ld: warning:
/tmp/polyobj.2070.o: missing .note.GNU-stack section implies executable
stack

Hi Jessica,

Looks like polyml is failing its autopkgtest. As the release happens is
happening soon, would you consider to take a quick look at this?

Thanks
Nilesh