Public bug reported:

Multiple build-time gzip tests are failing[1] on s390x only:

14:31:21[0]  Test: ./gzipwr_flushInterval.sh
------------------------------------------------------------
config rstb_615693_cea0d3b33SOB_.conf is:
     1  module(load="../plugins/imdiag/.libs/imdiag")
     2  global(inputs.timeout.shutdown="60000"
     3         default.action.queue.timeoutshutdown="20000"
     4         default.action.queue.timeoutEnqueue="20000")
     5  # use legacy-style for the following settings so that we can override 
if needed
     6  $MainmsgQueueTimeoutEnqueue 20000
     7  $MainmsgQueueTimeoutShutdown 10000
     8  $IMDiagListenPortFileName rstb_615693_cea0d3b33SOB.imdiag.port
     9  $IMDiagServerRun 0
    10  $IMDiagAbortTimeout 580
    11  
    12  :syslogtag, contains, "rsyslogd"  ./rstb_615693_cea0d3b33SOB.started
    13  ###### end of testbench instrumentation part, test conf follows:
    14  
    15  module(load="../plugins/imtcp/.libs/imtcp")
    16  input(type="imtcp" port="0" 
listenPortFileName="rstb_615693_cea0d3b33SOB.tcpflood_port")
    17  
    18  template(name="outfmt" type="string" string="%msg:F,58:2%\n")
    19  :msg, contains, "msgnum:" action(type="omfile" template="outfmt"
    20                                   zipLevel="6" ioBufferSize="256k"
    21                                   flushOnTXEnd="off" flushInterval="1"
    22                                   asyncWriting="on"
    23                                   
file="rstb_615693_cea0d3b33SOB.out.log.gz")
rsyslogd: NOTE: RSYSLOG_DEBUG_TIMEOUTS_TO_STDERR activated
main Q:Reg: worker start requested, num workers currently 0
main Q:Reg: wrkr start initiated with state 0, num workers now 1
rsyslog debug: main Q:Reg: worker 0x2aa3d545730 started
rsyslog debug: main Q:Reg: started with state 3, num workers now 1
14:31:21[0]  rstb_615693_cea0d3b33SOB:.pid found, pid 158902
14:31:21[0]  rsyslogd startup msg seen, pid  158902
waiting for file rstb_615693_cea0d3b33SOB.imdiag.port
imdiag port: 35981
waiting for file rstb_615693_cea0d3b33SOB.tcpflood_port
TCPFLOOD_PORT now: 37167
starting run 1
Sending 2500 messages.

00002500 messages sent
runtime: 0.001
End of tcpflood Run

gzip: rstb_615693_cea0d3b33SOB.out.log.gz: invalid compressed data--format 
violated
scanf error in index i=0

gzip: rstb_615693_cea0d3b33SOB.out.log.gz: invalid compressed data--format 
violated
sequence error detected in rstb_615693_cea0d3b33SOB.out.log.gz
number of lines in file: 0 rstb_615693_cea0d3b33SOB.out.log.gz
sorted data has been placed in error.log, first 10 lines are:
     1  scanf error in index i=0
---last 10 lines are:
     1  scanf error in index i=0
UNSORTED data, first 10 lines are:
     1  scanf error in index i=0
---last 10 lines are:
     1  scanf error in index i=0
not reporting failure as RSYSLOG_STATSURL is not set
rsyslog pid file still exists, trying to shutdown...
rsyslogd debug: info: trying to cooperatively stop input 
../plugins/imdiag/.libs/imdiag, timeout 60000 ms
rsyslogd debug: info: trying to cooperatively stop input imtcp, timeout 60000 ms
rsyslog debug: main Q:Reg/w0: enter WrkrExecCleanup
rsyslog debug: 0x2aa3d5458b0: worker exiting
rsyslog debug: main Q:Reg/w0: thread joined
14:31:26[5]  FAIL: Test ./gzipwr_flushInterval.sh (took 5 seconds)
FAIL gzipwr_flushInterval.sh (exit status: 1)


So far I have seen this in noble, while preparing an SRU[2]. Don't know yet if 
oracular or others are also affected.


1. 
https://launchpadlibrarian.net/752369377/buildlog_ubuntu-noble-s390x.rsyslog_8.2312.0-3ubuntu9.1~ppa1_BUILDING.txt.gz
2. https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2056768

** Affects: rsyslog (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: ftbfs

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083526

Title:
  FTBFS s390x: gzip: stdin: invalid compressed data--format violated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2083526/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to