Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upIntermittent test-wpt timeout in 2dcontext/drawing-images-to-the-canvas/* and mozilla/canvas/* #7787
Comments
|
Two other drawimage tests also timed out in that run.
|
|
|
|
I fear there's a recent regression behind this sudden spurt of new intermittent timeouts, if we haven't modified our build machine environments recently. |
|
Getting a lot of drawimage failures (#7948) |
Investigations for #7787 I'm just going to keep throwing stuff at try, because running directly on the builders isn't yielding results. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8314) <!-- Reviewable:end -->
|
The most recent log showed that we're calling |
Investigations for #7787 I'm just going to keep throwing stuff at try, because running directly on the builders isn't yielding results. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8314) <!-- Reviewable:end -->
Investigations for #7787 I'm just going to keep throwing stuff at try, because running directly on the builders isn't yielding results. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8314) <!-- Reviewable:end -->
Investigations for #7787 I'm just going to keep throwing stuff at try, because running directly on the builders isn't yielding results. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8314) <!-- Reviewable:end -->
Investigations for #7787 I'm just going to keep throwing stuff at try, because running directly on the builders isn't yielding results. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8314) <!-- Reviewable:end -->
Investigations for #7787 I'm just going to keep throwing stuff at try, because running directly on the builders isn't yielding results. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8314) <!-- Reviewable:end -->
Investigations for #7787 I'm just going to keep throwing stuff at try, because running directly on the builders isn't yielding results. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8314) <!-- Reviewable:end -->
|
According to the log in http://build.servo.org/builders/mac-rel-wpt/builds/281/steps/shell_2/logs/stdio the constellation never processes the query from the compositor. Fascinating. |
|
Most intriguingly, |
…ts on the build machines. Continuation of investigation for servo#7787.
Force constellation logging when running particularly frustrating tes… …ts on the build machines. Continuation of investigation for #7787. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8367) <!-- Reviewable:end -->
|
http://build.servo.org/builders/mac-rel-wpt/builds/304/steps/shell_2/logs/stdio shows zero output from constellation even with RUST_LOG=compositing::constellation ostensibly turned on, which is extremely confusing. |
|
Running the appropriate tests locally does show the |
|
Hasn't been seen in months, not disabled => close. |
This was related to servo#7787 that was closed because it didn't happen for a long time. We check whether that is the case for servo#8311 too.
This was related to servo#7787 that was closed because it didn't happen for a long time. We check whether that is the case for servo#8311 too.
This was related to servo#7787 that was closed because it didn't happen for a long time. We check whether that is the case for servo#8311 too.
This was related to servo#7787 that was closed because it didn't happen for a long time. We check whether that is the case for servo#8311 too.
Seen in #7778.