All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] LTP: accept02: BROK: accept02.c:52: setsockopt(6, 0, 42, 0xffff9c56df78, 136) failed: ENODEV (19)
Date: Wed, 30 Oct 2019 19:02:00 -0400 (EDT)	[thread overview]
Message-ID: <1277217234.9839643.1572476520526.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CA+G9fYv+-dz11fSjMNt8SHaAhRpu1F=8MF7ieS4ZASAwDzH7Eg@mail.gmail.com>



----- Original Message -----
> LTP syscall accept02 test failed intermittently on hikey arm64 device,
> qemu_x86_64 and qemu_i386.
> 
> Do you see this intermittent failure at your end ?

I'm not. What does the network look like on these systems?
Is there a default route? Is 224.0.0.0 reachable?

Can you check with?

# ip route 
# ip route get 224.0.0.0

> 
> hikey arm64 output log,
> 
> tst_test.c:1118: INFO: Timeout per run is 0h 15m 00s
> tst_buffers.c:55: INFO: Test is using guarded buffers
> accept02.c:127: INFO: Starting listener on port: 35903
> safe_net.c:186: BROK: accept02.c:52: setsockopt(6, 0, 42,
> 0xffff9c56df78, 136) failed: ENODEV (19)
> 
> qemu_x86_64 output log,
> 
> tst_test.c:1118: INFO: Timeout per run is 0h 15m 00s
> tst_buffers.c:55: INFO: Test is using guarded buffers
> accept02.c:127: INFO: Starting listener on port: 47245
> safe_net.c:186: BROK: accept02.c:52: setsockopt(6, 0, 42,
> 0x7f5397ca3f78, 136) failed: ENODEV (19)
> 
> Test results comparison,
> https://qa-reports.linaro.org/lkft/linux-mainline-oe/tests/ltp-syscalls-tests/accept02
> 
> Full test log,
> https://lkft.validation.linaro.org/scheduler/job/976363
> https://lkft.validation.linaro.org/scheduler/job/977681
> 
> Best regards
> Naresh Kamboju
> 


  reply	other threads:[~2019-10-30 23:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30  6:17 [LTP] LTP: accept02: BROK: accept02.c:52: setsockopt(6, 0, 42, 0xffff9c56df78, 136) failed: ENODEV (19) Naresh Kamboju
2019-10-30 23:02 ` Jan Stancek [this message]
2019-10-31  9:31   ` Naresh Kamboju
2019-10-31  9:45     ` Jan Stancek

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

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

  git send-email \
    --in-reply-to=1277217234.9839643.1572476520526.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.