{"push_id":858380332,"size":2,"distinct_size":2,"ref":"refs/heads/auto","head":"f74754f582fa8126eacb1fa423cd9db2325d8621","before":"3780fb7fe02ed66bd391421a0c5506b5635279dd","commits":[{"sha":"a3859c07263fae4d2367352af8775492d3e578b5","author":{"email":"05601062767d0179cbf4a4b8d745573eaf18782c@benshu.de","name":"benshu"},"message":"Fixed panic in ActiveTimers.set_timeout_or_interval.","distinct":true,"url":"https://api.github.com/repos/servo/servo/commits/a3859c07263fae4d2367352af8775492d3e578b5"},{"sha":"f74754f582fa8126eacb1fa423cd9db2325d8621","author":{"email":"1d30da7446c147361b50ba946a7897e87cc888f4@mozilla.com","name":"bors-servo"},"message":"Auto merge of #8175 - benschulz:set-timeout-panic, r=jdm\n\nFixed panic in ActiveTimers.set_timeout_or_interval.\n\n`ActiveTimers.set_timeout_or_interval` asserts that the pipeline is not currently frozen. Apparently that is too strict. When pending network requests complete after a pipeline is frozen, scripts may be executed and a timer scheduled.\n\nWith these changes scheduling a timer while the pipeline is frozen behaves as if the timer was scheduled at the time the pipeline was frozen.\n\nTo reproduce the panic\n 1. `./mach run -r http://google.com`,\n 2. immediately click on any link and\n 3. wait for the panic.\n\n<!-- Reviewable:start -->\n[<img src=\"https://reviewable.io/review_button.png\" height=40 alt=\"Review on Reviewable\"/>](https://reviewable.io/reviews/servo/servo/8175)\n<!-- Reviewable:end -->","distinct":true,"url":"https://api.github.com/repos/servo/servo/commits/f74754f582fa8126eacb1fa423cd9db2325d8621"}]}