{"action":"opened","issue":{"url":"https://api.github.com/repos/web-platform-tests/wpt/issues/14434","repository_url":"https://api.github.com/repos/web-platform-tests/wpt","labels_url":"https://api.github.com/repos/web-platform-tests/wpt/issues/14434/labels{/name}","comments_url":"https://api.github.com/repos/web-platform-tests/wpt/issues/14434/comments","events_url":"https://api.github.com/repos/web-platform-tests/wpt/issues/14434/events","html_url":"https://github.com/web-platform-tests/wpt/issues/14434","id":389219761,"node_id":"MDU6SXNzdWUzODkyMTk3NjE=","number":14434,"title":"Some User Timing tests are flaky","user":{"login":"foolip","id":498917,"node_id":"MDQ6VXNlcjQ5ODkxNw==","avatar_url":"https://avatars1.githubusercontent.com/u/498917?v=4","gravatar_id":"","url":"https://api.github.com/users/foolip","html_url":"https://github.com/foolip","followers_url":"https://api.github.com/users/foolip/followers","following_url":"https://api.github.com/users/foolip/following{/other_user}","gists_url":"https://api.github.com/users/foolip/gists{/gist_id}","starred_url":"https://api.github.com/users/foolip/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/foolip/subscriptions","organizations_url":"https://api.github.com/users/foolip/orgs","repos_url":"https://api.github.com/users/foolip/repos","events_url":"https://api.github.com/users/foolip/events{/privacy}","received_events_url":"https://api.github.com/users/foolip/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-10T09:51:56Z","updated_at":"2018-12-10T09:51:56Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"https://github.com/web-platform-tests/wpt/pull/14409#issuecomment-445753408 lists a number of tests in user-timing/ that were flaky in Firefox:\r\n\r\n\r\n|                              Test                             |                                                         Subtest                                                         |            Results            |                                                                                Messages                                                                                |\r\n|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\r\n| `/user-timing/measure_associated_with_navigation_timing.html` | `Second measure of current mark to navigationStart should be negative value.`                                           | **FAIL: 1/10, PASS: 9/10**    | `assert_true: Second measure of current mark to navigationStart should be negative value. expected true got false`                                                     |\r\n| `/user-timing/measure_associated_with_navigation_timing.html` | `Measure from domComplete event to most recent mark \"a\" should have longer duration.`                                   | **FAIL: 1/10, PASS: 9/10**    | `assert_true: Measure from domComplete event to most recent mark \"a\" should have longer duration. expected true got false`                                             |\r\n| `/user-timing/measure_associated_with_navigation_timing.html` | `Measure from most recent mark to navigationStart should have longer duration.`                                         | **FAIL: 1/10, PASS: 9/10**    | `assert_true: Measure from most recent mark to navigationStart should have longer duration. expected true got false`                                                   |\r\n\r\nSuggested method to investigate:\r\n1. Add a trailing whitespace or other no-op to all tests in user-timing/ in a test PR\r\n1. Check which were flaky on Taskcluster\r\n1. Fix them :)"}}
{"actor":{"display_login":"foolip"}}