Closed
Bug 1222284
Opened 9 years ago
Closed 7 years ago
Intermittent browser_permissionsPromptAllow.js | Test timed out, Found a tab after previous test timed out: browser_permissionsPrompt.html -
Categories
(Core :: Storage: IndexedDB, defect, P5)
Tracking
()
RESOLVED
FIXED
mozilla56
People
(Reporter: KWierso, Assigned: shawnjohnjr)
References
(Blocks 1 open bug)
Details
(Keywords: intermittent-failure)
Attachments
(3 files, 18 obsolete files)
3.27 KB,
patch
|
Details | Diff | Splinter Review | |
21.99 KB,
patch
|
Details | Diff | Splinter Review | |
700 bytes,
patch
|
Details | Diff | Splinter Review |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•8 years ago
|
Blocks: e10s-tests
tracking-e10s:
--- → ?
Updated•8 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•8 years ago
|
Summary: Intermittent browser_permissionsPromptAllow.js | Found a tab after previous test timed out: browser_permissionsPrompt.html - → Intermittent browser_permissionsPromptAllow.js | Test timed out, Found a tab after previous test timed out: browser_permissionsPrompt.html -
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → shuang
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 28•7 years ago
|
||
try to add more logs: https://treeherder.mozilla.org/#/jobs?repo=try&revision=94c4046fa2bee46f30d49e6816454f2160767ab7
Assignee | ||
Comment 29•7 years ago
|
||
log: https://public-artifacts.taskcluster.net/QBsCeMQKQtGjwl27n3GEWQ/0/public/logs/live_backing.log
Assignee | ||
Comment 30•7 years ago
|
||
(In reply to Shawn Huang [:shawnjohnjr] from comment #28) > try to add more logs: > https://treeherder.mozilla.org/#/ > jobs?repo=try&revision=94c4046fa2bee46f30d49e6816454f2160767ab7 https://treeherder.mozilla.org/logviewer.html#?job_id=111828186&repo=try&lineNumber=3101
Assignee | ||
Comment 31•7 years ago
|
||
19:40:55 INFO - TEST-START | dom/indexedDB/test/browser_permissionsPromptAllow.js 19:40:55 INFO - GECKO(33583) | !! test1 19:40:55 INFO - GECKO(33583) | !! test 1 creating tab 19:40:55 INFO - GECKO(33583) | !! test 1 addeventlistener 19:40:55 INFO - GECKO(33583) | loading test page: http://mochi.test:8888/browser/dom/indexedDB/test/browser_permissionsPrompt.html 19:40:55 INFO - GECKO(33583) | !! test 1 load 19:40:55 INFO - GECKO(33583) | !! wait for event 19:40:55 INFO - GECKO(33583) | !! in spawn 19:40:56 INFO - GECKO(33583) | !! got event 19:40:56 INFO - GECKO(33583) | !! event.type == success 19:40:56 INFO - GECKO(33583) | !! event.preventDefault(); 19:40:56 INFO - GECKO(33583) | !! finishTest 19:40:56 INFO - GECKO(33583) | xxxxxx done !! got finished callback 19:40:56 INFO - GECKO(33583) | !! resolve 19:40:56 INFO - GECKO(33583) | !! callback result, exception 19:40:56 INFO - GECKO(33583) | !! test 1 setFinishedCallback 19:40:56 INFO - GECKO(33583) | !! test 1 execute test2 19:40:56 INFO - GECKO(33583) | !! test2 19:40:56 INFO - GECKO(33583) | !! test 2 creating tab 19:40:56 INFO - GECKO(33583) | loading test page: http://mochi.test:8888/browser/dom/indexedDB/test/browser_permissionsPrompt.html 19:40:56 INFO - GECKO(33583) | !! test 2 load 19:40:56 INFO - GECKO(33583) | !! in spawn 19:40:56 INFO - GECKO(33583) | !! wait for event 19:40:56 INFO - GECKO(33583) | !! got event 19:40:56 INFO - GECKO(33583) | !! event.type == success 19:40:56 INFO - GECKO(33583) | !! event.preventDefault(); 19:40:56 INFO - GECKO(33583) | !! finishTest 19:41:40 INFO - GECKO(33583) | xxxxxx done 19:41:40 INFO - TEST-INFO | started process screencapture 19:41:41 INFO - TEST-INFO | screencapture: exit 0 19:41:41 INFO - Buffered messages logged at 19:40:55 19:41:41 INFO - creating tab 19:41:41 INFO - loading test page: http://mochi.test:8888/browser/dom/indexedDB/test/browser_permissionsPrompt.html 19:41:41 INFO - TEST-PASS | dom/indexedDB/test/browser_permissionsPromptAllow.js | prompt showing - 19:41:41 INFO - Buffered messages logged at 19:40:56 19:41:41 INFO - TEST-PASS | dom/indexedDB/test/browser_permissionsPromptAllow.js | prompt shown - 19:41:41 INFO - triggering main command 19:41:41 INFO - TEST-PASS | dom/indexedDB/test/browser_permissionsPromptAllow.js | at least one notification displayed - 19:41:41 INFO - triggering command: Allow Storing Data 19:41:41 INFO - TEST-PASS | dom/indexedDB/test/browser_permissionsPromptAllow.js | prompt hidden - 19:41:41 INFO - got finished callback 19:41:41 INFO - TEST-PASS | dom/indexedDB/test/browser_permissionsPromptAllow.js | First database creation was successful - 19:41:41 INFO - TEST-PASS | dom/indexedDB/test/browser_permissionsPromptAllow.js | No exception - 19:41:41 INFO - TEST-PASS | dom/indexedDB/test/browser_permissionsPromptAllow.js | Correct permission set - 19:41:41 INFO - creating tab 19:41:41 INFO - loading test page: http://mochi.test:8888/browser/dom/indexedDB/test/browser_permissionsPrompt.html 19:41:41 INFO - Buffered messages finished 19:41:41 INFO - TEST-UNEXPECTED-FAIL | dom/indexedDB/test/browser_permissionsPromptAllow.js | Test timed out -
Assignee | ||
Comment 32•7 years ago
|
||
How come "window.testFinishedCallback" is null in this case? good case 00:09:16 INFO - GECKO(19156) | !! test2 00:09:16 INFO - GECKO(19156) | !! test 2 creating tab 00:09:16 INFO - GECKO(19156) | loading test page: http://mochi.test:8888/browser/dom/indexedDB/test/browser_permissionsPrompt.html 00:09:16 INFO - GECKO(19156) | !! test 2 load 00:09:16 INFO - GECKO(19156) | !! wait for event 00:09:16 INFO - GECKO(19156) | !! in spawn 00:09:16 INFO - GECKO(19156) | !! got event 00:09:16 INFO - GECKO(19156) | !! event.type == success 00:09:16 INFO - GECKO(19156) | !! event.preventDefault(); 00:09:16 INFO - GECKO(19156) | !! finishTest 00:09:16 INFO - GECKO(19156) | !! entering finishTest() 00:09:16 INFO - GECKO(19156) | !! calling finishTestNow() 00:09:16 INFO - GECKO(19156) | xxxxxx done entering finishTestNow 00:09:16 INFO - GECKO(19156) | testGenerator return 00:09:16 INFO - GECKO(19156) | testGenerator = undefined 00:09:16 INFO - GECKO(19156) | !! entering setTimeout 00:09:16 INFO - GECKO(19156) | !! calling window.testFinishedCallback() 00:09:16 INFO - GECKO(19156) | !! got finished callback 00:09:16 INFO - GECKO(19156) | !! resolve 00:09:16 INFO - GECKO(19156) | !! callback result, exception 00:09:16 INFO - GECKO(19156) | !! test 2 setFinishedCallback 00:09:16 INFO - GECKO(19156) | !! test 2 execute finish 00:09:16 INFO - GECKO(19156) | entering finishTestNow bad case 00:10:06 INFO - GECKO(34055) | !! test2 00:10:06 INFO - GECKO(34055) | !! test 2 creating tab 00:10:07 INFO - GECKO(34055) | loading test page: http://mochi.test:8888/browser/dom/indexedDB/test/browser_permissionsPrompt.html 00:10:07 INFO - GECKO(34055) | !! test 2 load 00:10:07 INFO - GECKO(34055) | !! in spawn 00:10:07 INFO - GECKO(34055) | !! wait for event 00:10:07 INFO - GECKO(34055) | !! got event 00:10:07 INFO - GECKO(34055) | !! event.type == success 00:10:07 INFO - GECKO(34055) | !! event.preventDefault(); 00:10:07 INFO - GECKO(34055) | !! finishTest 00:10:07 INFO - GECKO(34055) | !! entering finishTest() 00:10:07 INFO - GECKO(34055) | !! calling finishTestNow() 00:10:07 INFO - GECKO(34055) | xxxxxx done entering finishTestNow 00:10:07 INFO - GECKO(34055) | testGenerator return 00:10:07 INFO - GECKO(34055) | testGenerator = undefined 00:10:07 INFO - GECKO(34055) | !! entering setTimeout 00:10:07 INFO - GECKO(34055) | !! calling window.testFinishedCallback is null 00:10:51 INFO - TEST-INFO | started process screencapture 00:10:51 INFO - TEST-INFO | screencapture: exit 0 00:10:51 INFO - Buffered messages logged at 00:10:06
Assignee | ||
Comment 33•7 years ago
|
||
Okay, so in the previous experience, log can't tell the execution sequence between chrome and content window. It's possible that testFinishedCallback() is executed after finishTest() from content is called. So window.testFinishedCallback is null.
Assignee | ||
Comment 34•7 years ago
|
||
Currently setFinishedCallback() problem impacts: Bug 1222282: dom/indexedDB/test/browser_forgetThisSite.js Bug 1222284: dom/indexedDB/test/browser_permissionsPromptAllow.js Bug 1334950: dom/indexedDB/test/browser_permissionsPromptWorker.js Bug 1224872: dom/indexedDB/test/browser_perwindow_privateBrowsing.js So I think it will be better to fix these tests since there are so many test cases failure on muli-e10s.
Assignee | ||
Comment 35•7 years ago
|
||
(In reply to Shawn Huang [:shawnjohnjr] from comment #33) > Okay, so in the previous experience, log can't tell the execution sequence > between chrome and content window. It's possible that testFinishedCallback() > is executed after finishTest() from content is called. So > window.testFinishedCallback is null. http://searchfox.org/mozilla-central/rev/e8f4f51cd543f203e9cb861cecb7545ac43c836c/dom/indexedDB/test/browserHelpers.js#31
Assignee | ||
Comment 36•7 years ago
|
||
I discussed with Jan, it should be okay to keep postMessage only instead of doing setFinishedCallback to avoid such race condition.
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 38•7 years ago
|
||
Assignee | ||
Comment 39•7 years ago
|
||
Assignee | ||
Comment 40•7 years ago
|
||
Assignee | ||
Comment 41•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Attachment #8886093 -
Attachment is obsolete: true
Assignee | ||
Comment 42•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Attachment #8886057 -
Attachment is obsolete: true
Assignee | ||
Comment 43•7 years ago
|
||
Assignee | ||
Comment 47•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Attachment #8885562 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886092 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886097 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886099 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886101 -
Flags: review?(btseng)
Assignee | ||
Comment 48•7 years ago
|
||
This is just syncing solution from bug 1324163 and remove setFinishedCallback. I guess it will make sense to ask Bevis to review.
Comment 49•7 years ago
|
||
Ok, I would probably consider to replace: content.location = testPageURL; with: gBrowser.selectedBrowser.loadURI(testPageURL); to be in sync what you've done recently.
Comment 50•7 years ago
|
||
Comment on attachment 8885562 [details] [diff] [review] Bug 1222284 - Part 1: Replace setFinishedCallback with waitForMessage in browser_permissionsPromptAllow.js Review of attachment 8885562 [details] [diff] [review]: ----------------------------------------------------------------- You still keep keep testResult and testException, but after setFinishedCallback removal, these two are not handled separately it seems. I think it should be somehow fixed/unified. ::: dom/indexedDB/test/head.js @@ +98,5 @@ > + /* eslint-disable no-undef */ > + function contentScript() { > + addEventListener("message", function(event) { > + sendAsyncMessage("testLocal:exception", > + {exception: event.data}); "exception" here can contain either result or exception, right ?
Comment 51•7 years ago
|
||
(In reply to Jan Varga [:janv] from comment #50) > You still keep keep testResult and testException, but after > setFinishedCallback removal, these two are not handled separately it seems. > I think it should be somehow fixed/unified. I think either waitForMessage() should get another argument for the exception or exception should be removed everywhere. I don't know what is better/doable since I don't have that much time. I'll let Bevis to decide ... Thanks guys.
Assignee | ||
Comment 52•7 years ago
|
||
(In reply to Jan Varga [:janv] from comment #49) > Ok, I would probably consider to replace: > content.location = testPageURL; > with: > gBrowser.selectedBrowser.loadURI(testPageURL); > > to be in sync what you've done recently. Sure. It makes sense.
Assignee | ||
Comment 53•7 years ago
|
||
(In reply to Jan Varga [:janv] from comment #51) > (In reply to Jan Varga [:janv] from comment #50) > > You still keep keep testResult and testException, but after > > setFinishedCallback removal, these two are not handled separately it seems. > > I think it should be somehow fixed/unified. > > I think either waitForMessage() should get another argument for the > exception or exception should be removed everywhere. I don't know what is > better/doable since I don't have that much time. > I'll let Bevis to decide ... > > Thanks guys. I will try to remove exception and keep only one variable. Thanks.
Assignee | ||
Comment 54•7 years ago
|
||
Comment on attachment 8885562 [details] [diff] [review] Bug 1222284 - Part 1: Replace setFinishedCallback with waitForMessage in browser_permissionsPromptAllow.js I will fix issues commented by Jan. Cancel review.
Attachment #8885562 -
Attachment is obsolete: true
Attachment #8885562 -
Flags: review?(btseng)
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Updated•7 years ago
|
Attachment #8886092 -
Attachment is obsolete: true
Attachment #8886092 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886097 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886097 -
Attachment is obsolete: true
Assignee | ||
Updated•7 years ago
|
Attachment #8886099 -
Attachment is obsolete: true
Attachment #8886099 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886101 -
Attachment is obsolete: true
Attachment #8886101 -
Flags: review?(btseng)
Assignee | ||
Comment 56•7 years ago
|
||
Assignee | ||
Comment 57•7 years ago
|
||
Assignee | ||
Comment 58•7 years ago
|
||
Assignee | ||
Comment 59•7 years ago
|
||
Assignee | ||
Comment 60•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Attachment #8886968 -
Attachment is obsolete: true
Assignee | ||
Updated•7 years ago
|
Attachment #8886965 -
Attachment is obsolete: true
Assignee | ||
Comment 61•7 years ago
|
||
Assignee | ||
Comment 62•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Attachment #8886964 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886971 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886966 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886967 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886972 -
Flags: review?(btseng)
Comment 63•7 years ago
|
||
Comment on attachment 8886964 [details] [diff] [review] Bug 1222284 - Part 1: Replace setFinishedCallback with waitForMessage in browser_permissionsPromptAllow.js Review of attachment 8886964 [details] [diff] [review]: ----------------------------------------------------------------- I'd like to see the patches to be arranged as followed and revisit them again: 1. Part 1 only includes the change in browserHelpers.js and head.js of all these parts at once to tell the reader what utility functions to be changed. 2. and Part 2 only includes the changes of these browser_*.(js|html) according to the new utility functions. You can have browser.ini in a standalone part 3. In addition, you can explain more about how the new layout of each browser test looks like in the commit message of part 1. For example, in patch: - waitForExplicitFinish() will be replaced with add_task(). - gBrowser.selectedBrowser.addEventListener() will be replaced with waitForMessage(). - testFinishedCallback, testResult, and testException will be unified to testResult. Then, we can focus on the review of patch part 2 after change of part 1 is reviewed.
Attachment #8886964 -
Flags: review?(btseng)
Assignee | ||
Comment 64•7 years ago
|
||
Sure. I will re-arrange the patch set :)
Assignee | ||
Updated•7 years ago
|
Attachment #8886966 -
Attachment is obsolete: true
Attachment #8886966 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886967 -
Attachment is obsolete: true
Attachment #8886967 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886971 -
Attachment is obsolete: true
Attachment #8886971 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886972 -
Attachment is obsolete: true
Attachment #8886972 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8886964 -
Attachment is obsolete: true
Assignee | ||
Comment 65•7 years ago
|
||
Assignee | ||
Comment 66•7 years ago
|
||
Assignee | ||
Comment 67•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Attachment #8887381 -
Attachment is obsolete: true
Assignee | ||
Comment 68•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Attachment #8887380 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8887384 -
Flags: review?(btseng)
Assignee | ||
Updated•7 years ago
|
Attachment #8887382 -
Flags: review?(btseng)
Assignee | ||
Comment 69•7 years ago
|
||
> In addition, you can explain more about how the new layout of each browser test looks like in the commit message of part 1.
> For example, in patch:
> - waitForExplicitFinish() will be replaced with add_task().
> - gBrowser.selectedBrowser.addEventListener() will be replaced with waitForMessage().
> - testFinishedCallback, testResult, and testException will be unified to testResult.
I prefer to put summary into Part 2.
Updated•7 years ago
|
Attachment #8887380 -
Flags: review?(btseng) → review+
Updated•7 years ago
|
Attachment #8887382 -
Flags: review?(btseng) → review+
Comment 70•7 years ago
|
||
Comment on attachment 8887384 [details] [diff] [review] Bug 1222284 - Part 2: Replace setFinishedCallback with waitForMessage for browser tests Review of attachment 8887384 [details] [diff] [review]: ----------------------------------------------------------------- r=me, after the following nits are addressed, thanks! ::: dom/indexedDB/test/browser_permissionsSharedWorker.html @@ +10,1 @@ > let testIsIDBDatabase; nit: we never use this variable. Please remove it as well. ::: dom/indexedDB/test/browser_permissionsWorker.html @@ +10,1 @@ > let testIsIDBDatabase; ditto.
Attachment #8887384 -
Flags: review?(btseng) → review+
Assignee | ||
Comment 71•7 years ago
|
||
(In reply to Bevis Tseng [:bevis][:btseng] from comment #70) > Comment on attachment 8887384 [details] [diff] [review] > Bug 1222284 - Part 2: Replace setFinishedCallback with waitForMessage for > browser tests > > Review of attachment 8887384 [details] [diff] [review]: > ----------------------------------------------------------------- > > r=me, after the following nits are addressed, thanks! > > ::: dom/indexedDB/test/browser_permissionsSharedWorker.html > @@ +10,1 @@ > > let testIsIDBDatabase; > > nit: we never use this variable. Please remove it as well. > > ::: dom/indexedDB/test/browser_permissionsWorker.html > @@ +10,1 @@ > > let testIsIDBDatabase; > > ditto. Sure. I was wondering if I need to do it but considering this is not related to the original issue, I choose to ignore it. I will remove it. Thanks!
Assignee | ||
Updated•7 years ago
|
Attachment #8887380 -
Attachment is obsolete: true
Assignee | ||
Updated•7 years ago
|
Attachment #8887382 -
Attachment is obsolete: true
Assignee | ||
Updated•7 years ago
|
Attachment #8887384 -
Attachment is obsolete: true
Assignee | ||
Comment 72•7 years ago
|
||
Assignee | ||
Comment 73•7 years ago
|
||
Assignee | ||
Comment 74•7 years ago
|
||
Assignee | ||
Comment 75•7 years ago
|
||
try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=1029ee532e3392b4131c19c47784031a90ada091
Assignee | ||
Comment 76•7 years ago
|
||
I'm not sure why try server is so slow. I will wait for a while anyway.
Comment 77•7 years ago
|
||
Pushed by shuang@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/e7ebcd8b7d58 Part 1: Replace setFinishedCallback with waitForMessage, r=btseng https://hg.mozilla.org/integration/mozilla-inbound/rev/c515128e7461 Part 2: Replace setFinishedCallback with waitForMessage for browser tests, r=btseng https://hg.mozilla.org/integration/mozilla-inbound/rev/3c96d3de9c7c Part 3: Enable test browser_permissionsPromptWorker.js again on mac, r=btseng
Assignee | ||
Comment 78•7 years ago
|
||
(In reply to Shawn Huang [:shawnjohnjr] from comment #75) > try: > https://treeherder.mozilla.org/#/ > jobs?repo=try&revision=1029ee532e3392b4131c19c47784031a90ada091 Running: OS X 10.10 opt 50+ times OS X 10.10 dgb 70+ times I did not see any indexeddb test cases failure. It looks good now.
Comment 79•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e7ebcd8b7d58 https://hg.mozilla.org/mozilla-central/rev/c515128e7461 https://hg.mozilla.org/mozilla-central/rev/3c96d3de9c7c
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox56:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla56
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
You need to log in
before you can comment on or make changes to this bug.
Description
•