Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jesec-libtorrent failing test #167854

Closed
NULLx76 opened this issue Apr 8, 2022 · 6 comments · Fixed by #169236
Closed

jesec-libtorrent failing test #167854

NULLx76 opened this issue Apr 8, 2022 · 6 comments · Fixed by #169236
Labels
0.kind: bug Something is broken

Comments

@NULLx76
Copy link
Member

NULLx76 commented Apr 8, 2022

Describe the bug

jesec-libtorrent tests fail, making the build fail.

Steps To Reproduce

Steps to reproduce the behavior:

  1. build jesec-libtorrent
  2. test fails, failing the build

Expected behavior

I expect it to build succesfully

Screenshots

image

image

Additional context

I'm building the package with the help of morph to deploy on a server, though this shouldn't really have an impact.

Notify maintainers

@winterqt @AndersonTorres

Metadata

[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.174-2-pve, NixOS, 22.05 (Quokka), 22.05pre-git`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.8.0pre20220322_d5d4d98`
 - channels(root): `"nixos-20.09.3246.d4189f68fdb"`
 - nixpkgs: `/home/victor/src/nixos-configs/nix-channel/nixpkgs`
@NULLx76 NULLx76 added the 0.kind: bug Something is broken label Apr 8, 2022
@winterqt
Copy link
Member

winterqt commented Apr 8, 2022

This happened between 2d7c764 and f22dc92.

I'll bisect later, thanks for the heads up!

@winterqt
Copy link
Member

winterqt commented Apr 8, 2022

The test is expecting EAI_NONAME to be returned by getaddrinfo("1.1.1.300"), but is instead getting EAI_AGAIN.

I'm... really not sure how to move forward with this, short of disabling the test.

@AndersonTorres
Copy link
Member

Next time copy-paste the error message.

@vcunat
Copy link
Member

vcunat commented Apr 10, 2022

Perhaps triggered by upgrading glibc from 2.33 to 2.34? (some change in getaddrinfo() behavior)

@winterqt
Copy link
Member

I ruled that out initially since I didn't see anything mentioned in the changelog about getaddrinfo. I'll give it a try, though.

@winterqt
Copy link
Member

This has been fixed by #169236.

@vcunat vcunat linked a pull request Apr 22, 2022 that will close this issue
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug Something is broken
Projects
None yet
4 participants