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

Builder curl-threaded-solaris10-sparc Build #2896

Results:

Failed runtest

SourceStamp:

Projectcurl
Repositoryhttps://github.com/curl/curl.git
Branchmaster
Revision8724306e78b399917f38e161cf97592377f45e8d
Got Revision8724306e78b399917f38e161cf97592377f45e8d
Changes1 change

BuildSlave:

unstable10s

Reason:

The SingleBranchScheduler scheduler named 'schedule-curl-threaded-solaris10-sparc' triggered this build

Steps and Logfiles:

  1. git update ( 26 secs )
    1. stdio
  2. Runtest './tests/testcurl.pl --nogitpull ...' failed ( 3 hrs, 57 mins, 14 secs )
    1. stdio
    2. resultlog
  3. Mail result 'cat resultlog ...' ( 1 secs )
    1. stdio

Build Properties:

NameValueSource
branch master Build
builddir /export/home/buildbot-unstable10s/slave/curl-threaded-solaris10-sparc slave
buildername curl-threaded-solaris10-sparc Builder
buildnumber 2896 Build
codebase Build
got_revision 8724306e78b399917f38e161cf97592377f45e8d Git
osplatform SPARC SetPropertyFromCommand Step
osrelease 10 SetPropertyFromCommand Step
project curl Build
repository https://github.com/curl/curl.git Build
revision 8724306e78b399917f38e161cf97592377f45e8d Build
scheduler schedule-curl-threaded-solaris10-sparc Scheduler
slavename unstable10s BuildSlave
workdir /export/home/buildbot-unstable10s/slave/curl-threaded-solaris10-sparc slave (deprecated)

Forced Build Properties:

NameLabelValue

Responsible Users:

  1. Daniel Stenberg

Timing:

StartTue Jul 8 10:47:50 2025
EndTue Jul 8 23:01:18 2025
Elapsed12 hrs, 13 mins, 28 secs

All Changes:

:

  1. Change #238698

    Category curl
    Changed by Daniel Stenberg <danielohnoyoudont@haxx.se>
    Changed at Tue 08 Jul 2025 10:14:45
    Repository https://github.com/curl/curl.git
    Project curl
    Branch master
    Revision 8724306e78b399917f38e161cf97592377f45e8d

    Comments

    runtests: support memory-limits per test
    The idea here is to set limits per test how many allocations and maximum
    amount of memory it is allowed to use. This is a means to make sure the
    number and total size of allocations are kept in check and don't
    mistakenly "blow up".
    
    If runtests.pl detects that the given limits have been exceeded it fails
    the test case with an error.
    
    The `<verify>` part now supports `<limits>`, and in this section two
    limits can be set for each test (verified in debug builds only):
    
        Allocations: [number of allocation calls]
        Maximum allocated: [maximum concurrent memory allocated]
    
    Default limits (used if nothing is set in the test file):
    
        Allocations: 1000
        Maximum allocated: 1000000
    
    Closes #17821

    Changed files

    • docs/tests/FILEFORMAT.md
    • tests/data/test1
    • tests/data/test1129
    • tests/data/test1156
    • tests/data/test1291
    • tests/data/test1559
    • tests/data/test1560
    • tests/data/test1651
    • tests/data/test2302
    • tests/data/test2303
    • tests/data/test2601
    • tests/data/test3207
    • tests/data/test440
    • tests/data/test442
    • tests/data/test445
    • tests/data/test497
    • tests/data/test500
    • tests/data/test575
    • tests/data/test747
    • tests/data/test751
    • tests/data/test993
    • tests/runtests.pl