unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Bruno Victal <mirai@makinata.eu>
To: 63618@debbugs.gnu.org
Cc: mirai@makinata.eu, ludo@gnu.org
Subject: [bug#63618] [PATCH WIP] Socat tests
Date: Sat, 20 May 2023 22:50:19 +0100	[thread overview]
Message-ID: <fc41352a-62bd-88fd-361a-9a847c372189@makinata.eu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2127 bytes --]

I've noticed that socat does have a test-suite (under a "test" target)
though I am having some trouble with some of the tests failures.

Going through the build log, there's some lines of interest:

Test 59:
--8<---------------cut here---------------start------------->8---
…
test  59 CHILDDEFAULT: child process default properties... FAILED:
 ./socat -t 0.1  -u exec:./procan -
…
--8<---------------cut here---------------end--------------->8---


In test 227, tests fail due to an absent /etc/services.
--8<---------------cut here---------------start------------->8---
…
test 227 EXECPTYKILL: exec:...,pty explicitely kills sub process... OK
grep: /etc/services: No such file or directory
test 228 TCP4SERVICE: echo via connection to TCP V4 socket... !port 1 timed out! FAILED:  ./socat:
 ./socat -t 0.1  TCP4-LISTEN:,reuseaddr PIPE &
2023/05/20 20:48:44 socat[8835] E empty port/service
 ./socat -t 0.1  stdin!!stdout TCP4:127.0.0.1:
2023/05/20 20:48:49 socat[8857] E empty port/service
test 229 EXCEED_FOPEN_MAX: more than FOPEN_MAX FDs in use... OK
…
--8<---------------cut here---------------end--------------->8---
Note: a similar failure was already observed in
d6f6b57766e95d2fa8af63d4460a2b303ca4d867.

I wonder if it's feasible to include /etc/services
in the build environment?


Test 418:
--8<---------------cut here---------------start------------->8---
…
test 418 ABSTRACT_USER: Is the fs related user option on ABSTRACT socket applied to FD... FAILED                                                                                                                                   
 ./socat ABSTRACT-LISTEN:temp,accept-timeout=0.1,user= FILE:/dev/null                                                                                                                                                              
2023/05/20 20:50:55 socat[12189] E getpwnam(""): no such user
…
--8<---------------cut here---------------end--------------->8---


I'm out of clues as to how to get these 3 tests sorted out.
Any ideas?

I've attached the build logs for socat with the tests enabled below.


Regards,
Bruno

[-- Attachment #2: 2y5a746gxzg94kmsg7qv107vj952mj-socat-1.7.4.3.drv.lz --]
[-- Type: application/x-lzip, Size: 14705 bytes --]

             reply	other threads:[~2023-05-20 21:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-20 21:50 Bruno Victal [this message]
2023-05-20 21:52 ` [bug#63618] [PATCH WIP] gnu: socat: Enable tests Bruno Victal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fc41352a-62bd-88fd-361a-9a847c372189@makinata.eu \
    --to=mirai@makinata.eu \
    --cc=63618@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).