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

Builder linux-rel-css Build #5384

Results:

Build successful

SourceStamp:

Projectservo/servo
Repositoryhttps://github.com/servo/servo
Branchauto
Revision3ed6c22e45df06bf381356b394d01493fc0322a2
Got Revision3ed6c22e45df06bf381356b394d01493fc0322a2
Changes1 change

BuildSlave:

servo-linux1

Reason:

The AnyBranchScheduler scheduler named 'servo-auto' triggered this build

Steps and Logfiles:

  1. git update ( 4 secs )
    1. stdio
  2. generic generic ( 0 secs )
    1. - no logs -
  3. generic_1 generic_1 ( 0 secs )
    1. - no logs -
  4. shell 'pkill -x ...' ( 0 secs )
    1. stdio
  5. shell__1 './mach clean-nightlies ...' ( 8 secs )
    1. stdio
  6. compile ran build --release --with-debug-assertions ( 18 mins, 2 secs )
    1. - no logs -
  7. test ran test-css --release --processes 16 --always-succeed ( 11 mins, 30 secs )
    1. css-errorsummary.log
  8. shell__2 './mach filter-intermittents ...' ( 0 secs )
    1. stdio
    2. filtered-css-errorsummary.log
    3. intermittents.log
  9. compile__1 ran build-cef --release --with-debug-assertions ( 37 secs )
    1. stdio
  10. compile__2 ran build-geckolib --release ( 5 mins, 20 secs )
    1. stdio
  11. test__1 ran test-stylo --release warnings ( 50 secs )
    1. warnings (2)
  12. shell__3 'bash ./etc/ci/lockfile_changed.sh' ( 0 secs )
    1. stdio
  13. shell__4 'bash ./etc/ci/manifest_changed.sh' ( 0 secs )
    1. stdio

Build Properties:

NameValueSource
branch auto Build
builddir /home/servo/buildbot/slave/linux-rel-css slave
buildername linux-rel-css Builder
buildnumber 5384 Build
codebase Build
got_revision 3ed6c22e45df06bf381356b394d01493fc0322a2 Git
project servo/servo Build
repository https://github.com/servo/servo Build
revision 3ed6c22e45df06bf381356b394d01493fc0322a2 Build
scheduler servo-auto Scheduler
slavename servo-linux1 BuildSlave
warnings-count 2 WarningCountingShellCommand
workdir /home/servo/buildbot/slave/linux-rel-css slave (deprecated)

Forced Build Properties:

NameLabelValue

Responsible Users:

  1. bors-servo

Timing:

StartFri Aug 11 20:19:58 2017
EndFri Aug 11 20:56:34 2017
Elapsed36 mins, 35 secs

All Changes:

:

  1. Change #57535

    Category None
    Changed by bors-servo <lbergstrom+borsohnoyoudont@mozilla.com>
    Changed at Fri 11 Aug 2017 20:12:09
    Repository https://github.com/servo/servo
    Project servo/servo
    Branch auto
    Revision 3ed6c22e45df06bf381356b394d01493fc0322a2

    Comments

    Auto merge of #18051 - edunham:cleannightly, r=larsbergstrom
    
    Continue after failed attempt to delete old nightly
    
    Failure to catch this error broke bholley's PR https://github.com/servo/servo/pull/18048
    
    http://build.servo.org/builders/linux-dev/builds/8616/steps/shell__1/logs/stdio.
    Logs below for posterity.
    
    ```
    Current Rust nightly version: 599be0d18f4c6ddf36366d2a5a2ca6dc65886896
    Current Rust stable version: 1.19.0
    Removing /home/servo/.servo/cargo/13d94d5fa8129a34f5c77a1bcd76983f5aed2434
    Error running mach:
    
        ['clean-nightlies', '--keep', '3', '--force']
    
    The error occurred in code that was called by the mach command. This is either
    a bug in the called code itself or in the way that mach is calling it.
    
    You should consider filing a bug for this issue.
    
    If filing a bug, please include the full output of mach, including this error
    message.
    
    The details of the failure are as follows:
    
    OSError: [Errno 2] No such file or directory:
    '/home/servo/.servo/cargo/13d94d5fa8129a34f5c77a1bcd76983f5aed2434'
    
      File
    "/home/servo/buildbot/slave/linux-dev/build/python/servo/bootstrap_commands.py",
    line 334, in clean_nightlies
        delete(full_path)
      File "/home/servo/buildbot/slave/linux-dev/build/python/servo/util.py", line
    28, in delete
        os.remove(path)
    ```
    
    I don't know how the builder got into the edge case where the old nightly wasn't there for deletion, but in the case that removal fails for some reason, mach should just keep going. In the incredibly unlikely event that the failure to remove the file has consequences down the line, we'll have the failed remove in the log for troubleshooting.
    
    Also this passed tidy so if I failed to python I'll need to fix tidy as well as this.
    
    <!-- Reviewable:start -->
    ---
    This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/18051)
    <!-- Reviewable:end -->

    Changed files

    • python/servo/bootstrap_commands.py