I could successfully run |mach xpcshell-test| *LOCALLY* on August 25th. The summary lines from the test are shown below. 666:27.62 INFO INFO | Result summary: 666:27.62 INFO INFO | Passed: 3189 666:27.62 INFO INFO | Failed: 8 666:27.62 INFO INFO | Todo: 4 666:27.62 INFO INFO | Retried: 14 666:27.62 SUITE_END Betwenn August 25 and a few days ago, something has changed and now I get the following errors during my *LOCAL* run of xpcshell-test. However, the remote tryserver DOES NOT such errors. See, for example, https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=66ef3c2b0a7daf6d91aba1af924ca769f8cd282e I am stumped to see where to look. Running xpcshell-test successfully is very important to check the sanity of my local patches before submission. Also, sometimes I have to run debugger and other tools to figure out what is wrong with my patch that fails the tests. This I cannot do with tryserver run. My environment is the latest Debian GNU/Linux that runs inside virtualbox hosted on Windows 10 Pro. uname -a Linux ip030 5.2.0-2-amd64 #1 SMP Debian 5.2.9-2 (2019-08-21) x86_64 GNU/Linux I am mentioning the Debian name because I suspect it *could* be related to some security setting that may hinder some local daemon to operate correctly? From the attached log, I see error such as - timedout tests, - SQL syntax errors which seem to be lacking an indetifier somehow, - " ERROR Unexpected exception Error: IndexedDB clear() The operation failed for reasons unrelated to the database itself and not covered by any other error code. at resource://services-common/kinto-offline-client.js:603" - etc. OR, is |mach xpcshell-test| no longer intenteded to execute locally? I mean some tests in |make mozmill| seem to assume certain daemons running on certain ports which may collide with my local daemons. (and as a matter of fact, |make mozmill| seemed to use example.{org,com} domain names thinking that it won't collide with tester's domain: unfortunately, I used the said domain names within my firewall on this computer and thus some test inevitably failed until I chaned my local domain within my firewall to |example.localdomain|. So there can be various issues related to system setting. I also recall something about new javascript-based DB being substituted for mork database, and that may explain I see many errors related to kinto-offline-client.js. Any tips to look into this issue are appreciated.
Bug 1589779 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I could successfully run |mach xpcshell-test| *LOCALLY* on August 25th. The summary lines from the test are shown below. 666:27.62 INFO INFO | Result summary: 666:27.62 INFO INFO | Passed: 3189 666:27.62 INFO INFO | Failed: 8 666:27.62 INFO INFO | Todo: 4 666:27.62 INFO INFO | Retried: 14 666:27.62 SUITE_END Betwenn August 25 and a few days ago, something has changed and now I get the following errors during my *LOCAL* run of xpcshell-test. (Ouch forgot to insert this initially. Sorry.) 225:05.14 INFO INFO | Result summary: 225:05.14 INFO INFO | Passed: 3121 225:05.14 INFO INFO | Failed: 127 225:05.14 INFO INFO | Todo: 4 225:05.14 INFO INFO | Retried: 131 225:05.14 SUITE_END However, the remote tryserver DOES NOT such errors. See, for example, https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=66ef3c2b0a7daf6d91aba1af924ca769f8cd282e I am stumped to see where to look. Running xpcshell-test successfully is very important to check the sanity of my local patches before submission. Also, sometimes I have to run debugger and other tools to figure out what is wrong with my patch that fails the tests. This I cannot do with tryserver run. My environment is the latest Debian GNU/Linux that runs inside virtualbox hosted on Windows 10 Pro. uname -a Linux ip030 5.2.0-2-amd64 #1 SMP Debian 5.2.9-2 (2019-08-21) x86_64 GNU/Linux I am mentioning the Debian name because I suspect it *could* be related to some security setting that may hinder some local daemon to operate correctly? From the attached log, I see error such as - timed out tests, - SQL syntax errors which seem to be lacking an indentifier somehow, - " ERROR Unexpected exception Error: IndexedDB clear() The operation failed for reasons unrelated to the database itself and not covered by any other error code. at resource://services-common/kinto-offline-client.js:603" - etc. OR, is |mach xpcshell-test| no longer intenteded to execute locally? I mean some tests in |make mozmill| seem to assume certain daemons running on certain ports which may collide with my local daemons. (and as a matter of fact, |make mozmill| seemed to use example.{org,com} domain names thinking that they won't collide with tester's domain: unfortunately, I used the said domain names within my firewall on this computer and thus some test inevitably failed until I changed my local domain within my firewall to |example.localdomain|. Hmm... So there can be various issues related to system setting that may have changed on my end without my knowning due to package upgrade of Debian GNU/Linux. I also recall something about new javascript-based DB being substituted for mork database, and that may explain I see many errors related to kinto-offline-client.js. Any tips to look into this issue are appreciated.