Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Builder memcached-solaris10-amd64 Build #268

Results:

Failed shell_2 shell_3

SourceStamp:

Projectmemcached
Repositorygit://github.com/memcached/memcached.git
Branchnext
Revisione5817664738e613155078ddea66c9dde73339ac1
Got Revisione5817664738e613155078ddea66c9dde73339ac1
Changes1 change

BuildSlave:

unstable10x

Reason:

The SingleBranchScheduler scheduler named 'schedule-memcached-solaris10-amd64' triggered this build

Steps and Logfiles:

  1. git update ( 2 secs )
    1. stdio
  2. shell 'bash autogen.sh' ( 3 secs )
    1. stdio
  3. shell_1 './configure --enable-sasl ...' ( 6 secs )
    1. stdio
    2. config.log
  4. shell_2 'gmake' failed ( 0 secs )
    1. stdio
  5. shell_3 'gmake test' failed ( 0 secs )
    1. stdio

Build Properties:

NameValueSource
branch next Build
builddir /export/home/buildbot/slave/memcached-solaris10-amd64 slave
buildername memcached-solaris10-amd64 Builder
buildnumber 268 Build
codebase Build
got_revision e5817664738e613155078ddea66c9dde73339ac1 Git
project memcached Build
repository git://github.com/memcached/memcached.git Build
revision e5817664738e613155078ddea66c9dde73339ac1 Build
scheduler schedule-memcached-solaris10-amd64 Scheduler
slavename unstable10x BuildSlave
workdir /export/home/buildbot/slave/memcached-solaris10-amd64 slave (deprecated)

Forced Build Properties:

NameLabelValue

Responsible Users:

  1. dormando

Timing:

StartFri Oct 30 00:50:28 2020
EndFri Oct 30 00:50:41 2020
Elapsed13 secs

All Changes:

:

  1. Change #117241

    Category memcached
    Changed by dormando <dormandoohnoyoudont@rydia.net>
    Changed at Fri 30 Oct 2020 00:41:24
    Repository git://github.com/memcached/memcached.git
    Project memcached
    Branch next
    Revision e5817664738e613155078ddea66c9dde73339ac1

    Comments

    logger: fix spurious watcher hangups
    of course the previous commit didn't actually fix the bug: during
    poll() call we weren't filtering for the right watcher when we were
    polling a specific one. This could lead to reading a POLLHUP on the
    wrong socket and other issues.
    
    hopefully that solves some mysteries with the watcher system.

    Changed files

    • logger.c
    • t/watcher.t