Builder linux-rel-wpt Build #13814

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git update ( 3 secs )
   1. - no logs -
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 ...' ( 15 secs )
   1. stdio
6. shell__2 './mach clean-cargo-cache ...' ( 0 secs )
   1. stdio
7. shell__3 './etc/ci/clean_build_artifacts.sh' ( 0 secs )
   1. stdio
8. compile ran build --release --with-debug-assertions -p servo ( 13 mins, 9 secs )
   1. - no logs -
9. test ran test-wpt-failure ( 0 secs )
   1. stdio
10. test__1 ran test-wpt --release --processes 24 --total-chunks 2 --this-chunk 1 --always-succeed ( 18 mins, 12 secs )
    1. - no logs -
11. shell__4 './mach filter-intermittents ...' ( 0 secs )
    1. stdio
    2. filtered-wpt-errorsummary.log
12. test__2 ran test-wpt --release --binary-arg=--multiprocess --processes 24 eventsource ( 8 secs )
    1. wpt-mp-errorsummary.log
13. test__3 ran test-wpt --release --product=servodriver --headless tests/wpt/mozilla/tests/mozilla/DOMParser.html tests/wpt/mozilla/tests/css/per_glyph_font_fallback_a.html tests/wpt/mozilla/tests/css/img_simple.html tests/wpt/mozilla/tests/mozilla/secure.https.html ( 13 secs )
    1. stdio
14. test__4 ran test-wpt --release --product=servodriver --headless bluetooth ( 5 mins, 6 secs )
    1. bluetooth-errorsummary.log
15. test__5 ran test-wpt --release --headless --timeout-multiplier=4 --always-succeed webdriver ( 3 mins, 35 secs )
    1. wdspec-errorsummary.log
16. shell__5 './mach filter-intermittents ...' ( 0 secs )
    1. stdio
    2. filtered-wdspec-errorsummary.log
    3. intermittents.log
17. shell__6 './etc/ci/clean_build_artifacts.sh' ( 0 secs )
    1. stdio

Build Properties:

Forced Build Properties:

Responsible Users:

1. bors-servo

   lbergstrom+borsohnoyoudont@mozilla.com

Timing:

All Changes:

:

1. Change #125119

   Category	None
   Changed by	bors-servo <lbergstrom+borsohnoyoudont@mozilla.com>
   Changed at	Thu 17 Oct 2019 00:02:13
   Repository	https://github.com/servo/servo
   Project	servo/servo
   Branch	auto
   Revision	14240bee81bc8b5c5a55d1ed5d5719cf8ee342ee

   Comments

   Auto merge of #24452 - Manishearth:raf-lifecycle, r=asajeffrey
   
   Always request new XR frames
   
   Currently we only request XR frames when there is a rAF callback queued up.
   
   This is incorrect, see https://immersive-web.github.io/webxr/#xr-animation-frame
   
   With this change we always request updated frame state regardless of whether or not the user has queued up callbacks.
   
   In addition to being spec-correct, this means that we can reliably listen for events in the OpenXR backend in the rAF loop itself, instead of having to set up a second spinning loop for when the rAF is inactive. This lets us implement visibility states for openxr without having to worry about the user never receiving the wakeup call because the rAF loop isn't pumping.
   
   See also: https://github.com/immersive-web/webxr/issues/877
   
   r? @asajeffrey

   Changed files

   • components/script/dom/xrsession.rs