Builder rsyslog-solaris10-i386 Build #1862

Results:

Failed

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-rsyslog-solaris10-i386' triggered this build

Steps and Logfiles:

1. git updating ( 1 mins, 2 secs )
   1. stdio
2. shell  
   1. - no logs -
3. shell_1  
   1. - no logs -
4. shell_2  
   1. - no logs -
5. shell_3  
   1. - no logs -

Build Properties:

Forced Build Properties:

Responsible Users:

1. Rainer Gerhards

   rgerhardsohnoyoudont@adiscon.com

Timing:

All Changes:

:

1. Change #217336

   Category	rsyslog
   Changed by	Rainer Gerhards <rgerhardsohnoyoudont@adiscon.com>
   Changed at	Tue 31 Dec 2024 10:29:00
   Repository	https://github.com/rsyslog/rsyslog.git
   Project	rsyslog
   Branch	master
   Revision	08501b930fa02244e3edd07db0f0c727c0b980e2

   Comments

   CI: add check for compile with -std=gnu23 gcc option
   Note: The upcoming gnu23 C standard is overdoing it with type-safety. Inside
   rsyslog, we historically have method tables for generic calls, which
   keeps the code small and easy to understand. This would not decently be
   possible with the new type-safety requirements.
   
   So this commit works around these warning in a way that pretends to
   provide more type safety. We have done this in the least intrusive
   way to reduce the risk for regressions in code that works well in
   since decades. Also note that the code already does parameter
   validation.
   
   There would have been more elaborate ways to make gnu23 compile happy,
   e.g. by using a union of structs to provide the data element. Some folks
   consider this type safe. In reality, it is not a bit better than
   traditional C without types at all. Because the caller still needs to
   ensure it picks the right struct from the union. As this approach
   would also have larger regeression potential, we have not used it.
   
   Right now, we have suppressed some of the new warnings, as working
   around them would have required an even larger time budget and
   potentially larger regression potential. In the long term we may
   want to look into enabling them, as they would potentially be
   beneficial for new code not involving method tables.
   
   Some nits, however, were detected and have been fixed.
   
   This patch also "fixes" some false positive test failures, mostly
   be disabling some test functionality after confirmation these are
   flakes.
   
   see also https://github.com/rsyslog/rsyslog/issues/5507

   Changed files

   • .github/workflows/ci_compile.yml
   • runtime/cfsysline.c
   • runtime/linkedlist.c
   • runtime/linkedlist.h
   • runtime/obj-types.h
   • runtime/obj.c
   • runtime/obj.h
   • runtime/queue.c
   • runtime/rsconf.c
   • runtime/rsyslog.h
   • runtime/ruleset.c
   • tests/sndrcv_tls_anon_rebind.sh
   • tests/sndrcv_tls_client_missing_cert.sh
   • threads.c
   • tools/iminternal.c

2. Change #217337

   Category	rsyslog
   Changed by	Rainer Gerhards <rgerhardsohnoyoudont@adiscon.com>
   Changed at	Tue 31 Dec 2024 11:53:47
   Repository	https://github.com/rsyslog/rsyslog.git
   Project	rsyslog
   Branch	master
   Revision	f0965735766588d17424ad45ee09bf2aa2c25139

   Comments

   Merge pull request #5514 from rgerhards/gnu23-workaround
   Gnu23 workaround

   Changed files

   • no files

3. Change #217338

   Category	rsyslog
   Changed by	Rainer Gerhards <rgerhardsohnoyoudont@adiscon.com>
   Changed at	Tue 31 Dec 2024 11:55:37
   Repository	https://github.com/rsyslog/rsyslog.git
   Project	rsyslog
   Branch	master
   Revision	9135db7f0ac7015e38fa46634d5936328bf413bb

   Comments

   maintain ChangeLog

   Changed files

   • ChangeLog