Failure in 'test_multiread'

Bug #1794224 reported by Christian Ehrhardt 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
strongswan (Ubuntu)
New
Undecided
Unassigned

Bug Description

Builds without a source change now trigger the following:

  Running suite 'watcher':
    Running case 'read': +
    Running case 'write': +
    Running case 'multiread': -
      Failure in 'test_multiread': timeout(14) (i = 0)
 dumping 6 stack frame addresses:
  /lib/x86_64-linux-gnu/libpthread.so.0 @ 0x7f34766c5000 (__send+0x5e) [0x7f34766d701e]
    -> ??:?
  /<<PKGBUILDDIR>>/src/libstrongswan/tests/.libs/libstrongswan_tests @ 0x5598580f3000 [0x5598581285da]
    -> ??:0
  /<<PKGBUILDDIR>>/src/libstrongswan/tests/.libs/libstrongswan_tests @ 0x5598580f3000 [0x55985815015b]
    -> ??:0
  /<<PKGBUILDDIR>>/src/libstrongswan/tests/.libs/libstrongswan_tests @ 0x5598580f3000 [0x5598581506bf]
    -> ??:0
  /lib/x86_64-linux-gnu/libc.so.6 @ 0x7f34764db000 (__libc_start_main+0xeb) [0x7f34764ff09b]
    -> ??:?
  /<<PKGBUILDDIR>>/src/libstrongswan/tests/.libs/libstrongswan_tests @ 0x5598580f3000 [0x559858105f7a]
    -> ??:0
    Running case 'multiwrite': +
  Passed 3/4 'watcher' test cases

This might be due to new toolchain or library versions.
I'll start an investigation of that.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Those builds used to be very reliable so far but recently started to "sometimes" break on:
  Failure in 'test_multiread': timeout(14) (i = 0)

I started to work on that in bug 1794224 , but it has all the same symptoms than this issue here.
- showed up recently
- build time test timeout error
- not reproducible locally (too fast?)

Although it is not doing "much" disk I/O at the time I think I'll dup and track it together with bug 1794059

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.