java-kafka-clients fails test on CI

  • Open
  • quality assurance status badge
Details
2 participants
  • Björn Höfling
  • Marius Bakke
Owner
unassigned
Submitted by
Marius Bakke
Severity
normal
Merged with
M
M
Marius Bakke wrote on 11 Apr 2020 16:26
(address . bug-guix@gnu.org)
87v9m6hze8.fsf@devup.no
Guix,

'java-kafka-clients' fails a single test
"org.apache.kafka.common.memory.GarbageCollectedMemoryPoolTest" on the
Berlin build farm. Possibly due to the large amount of memory on these
systems? I have not been able to reproduce the failure.

Build log:

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl6R048ACgkQoqBt8qM6
VPpETQf/fefZvBdsfvz16MUOIazUh6qsrZc4mVskOMdKTpoUbfrK/aazg2MuANZ4
E94B8f5VldegE6DYuCe7IKX7Qg36uw3IAeInMG5QSpLJWkLdfN5FO11OlCmsP6S8
V3ND9nZ+AwEzRH1RjHlabEvxLHDDUAvSOfBOTBWv4U8ICF/Q7FZ59hUgXl6Bt40S
ybBLXjuthGbynRomyZmLgX5jDdUTULF7jMtwU0x8n7CUPDWCuYXzRpuXN7iodAKS
9zpXVPNRhrt7REeh7d7sCdochxY0Xp6LXrWORycbZcxc5TbldPX5tY9fy3p+q3fD
XpZ1Swjab8z38QovHjvHicBMkRQ4fA==
=Qinq
-----END PGP SIGNATURE-----

B
B
Björn Höfling wrote on 28 Apr 2020 19:58
merge 40554 40718
(address . control@debbugs.gnu.org)
20200428195835.12c2a421@alma-ubu
merge 40554 40718
end
-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQQiGUP0np8nb5SZM4K/KGy2WT5f/QUCXqhuywAKCRC/KGy2WT5f
/ZEhAJ0TpkyDSNS+vo3jfpzYY+X924FKeACfephLgWRRkIraxCle2em19OBVXRk=
=xA5x
-----END PGP SIGNATURE-----


M
M
Marius Bakke wrote on 19 May 2020 20:17
Re: bug#41396: java-kafka-clients fails tests
87pnazrdqa.fsf@devup.no
merge 41396 40718
thanks

Ricardo Wurmus <rekado@elephly.net> writes:

Toggle quote (10 lines)
> java-kafka-clients has a failing test:
>
> [junit] Running org.apache.kafka.common.network.SslTransportLayerTest
> [junit] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> [junit] SLF4J: Defaulting to no-operation (NOP) logger implementation
> [junit] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> [junit] Tests run: 31, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 8.072 sec
>
> The SLF4J failure seems to be unrelated (other tests also have this warning).

It only seems to happen on big-memory systems (but consistently so).
Björn did some investigation here:


If you can reproduce it, please help! :-)
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 40554@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 40554
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch