Builder rsyslog-solaris10-i386 Build #1848

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. Cropi

   alakatosohnoyoudont@redhat.com
2. Rainer Gerhards

   rgerhardsohnoyoudont@adiscon.com

Timing:

All Changes:

:

1. Change #214054

   Category	rsyslog
   Changed by	Cropi <alakatosohnoyoudont@redhat.com>
   Changed at	Fri 25 Oct 2024 14:54:11
   Repository	https://github.com/rsyslog/rsyslog.git
   Project	rsyslog
   Branch	master
   Revision	567b315d69c7219e15b9e4c8f81aa1002362d908

   Comments

   imjournal: Fix first message loss after journal rotation
   Previously, upon detecting a journal rotation, the pointer
   did not correctly advance to the next log entry, causing
   the first new message to be missed. This update ensures
   that the cursor is advanced correctly, allowing all entries
   to be read without skipping the first message after rotation.
   
   Two calls to sd_journal_next() — one in handleRotation and
   another in doRun caused the first message after rotation
   to be skipped."

   Changed files

   • plugins/imjournal/imjournal.c

2. Change #214055

   Category	rsyslog
   Changed by	Rainer Gerhards <rgerhardsohnoyoudont@adiscon.com>
   Changed at	Fri 15 Nov 2024 12:21:41
   Repository	https://github.com/rsyslog/rsyslog.git
   Project	rsyslog
   Branch	master
   Revision	7ec5d7a2e03accab2ddd20f3e8b2ad213991cbda

   Comments

   Merge pull request #5477 from Cropi/imjournal-reworked
   imjournal: Fix first message loss after journal rotation

   Changed files

   • no files