Interesting. With the change to the timeout to marionette.py in the previous comment (comment 26) and a slightly different parameters passed to valgrind, it seems that the first few tests seem to proceed to a point where the calendar test is shown on the screen and proceed very slowly. (there are errors obviously due to timeouts still, but that can be handled by longer timeout where it matters, I hope). But I am not holding my breath. Many tests failed due to timeout (see the excerpt from the log at the end.). I have not analyzed much yet. And based on my previous experience, I think the full test runs for like 2 days. Yes DAYS (not hours). I have no idea what else has changed in M-C/C-C to make this possible. But this is a great start. The results from the first several tests. The whole mochitest is still running. Output from ```egrep "(Subtests passed|Running on|/mach)" t9.list ``` (<- t9.list contains a partial log from the valgrind run). ``` 20:34.24 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 34:11.90 TEST_END: Test OK. Subtests passed 13/16. Unexpected 3 39:40.61 TEST_END: Test OK. Subtests passed 31/35. Unexpected 1 41:05.25 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 57:59.68 TEST_END: Test OK. Subtests passed 6/8. Unexpected 2 61:36.10 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 77:41.40 TEST_END: Test OK. Subtests passed 4/6. Unexpected 2 80:54.94 TEST_END: Test OK. Subtests passed 3/6. Unexpected 3 82:07.06 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 95:26.38 TEST_END: Test OK. Subtests passed 1/2. Unexpected 1 102:38.05 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 117:17.64 TEST_END: Test OK. Subtests passed 1/2. Unexpected 1 121:19.88 TEST_END: Test OK. Subtests passed 37/39. Unexpected 2 123:09.01 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 140:31.91 TEST_END: Test OK. Subtests passed 31/33. Unexpected 2 142:55.68 TEST_END: Test OK. Subtests passed 21/24. Unexpected 3 143:39.95 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 158:58.01 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1 161:33.68 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1 164:11.30 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 180:17.64 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1 182:25.29 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1 184:42.15 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. ``` I forgot exactly where this 2960 is set. Maybe it is default of |mach| when it invokes valgrind(?). Or it may be possible I have applied a local patch to increase this number already. But as in previous comment, (comment 26), I have not increased the timeout in marionette.py before. (Come to think of it, I only looked at scripts under mozilla/comm directory and missed this timeout value in marionette.py which is mozilla/testing/marionette/client/marionette_driver/marionette.py) The mochitest is still running slowly, but I have changed the time out in marionette.py from 1800 to 2400 and will see how the test failures will diminish. Somewhat great news so that more memory-related issues can be found for TB by running it under valgrind during mochitest. (Somehow TB under valgrind has run successfully since early this year for xpcshell tests already.)
Bug 1629433 Comment 27 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Interesting. With the change to the timeout to marionette.py in the previous comment (comment 26) and a slightly different parameters passed to valgrind, it seems that the first few tests in mochitest suite seem to proceed to a point where the calendar test is shown on the screen and proceed very slowly. (there are errors obviously due to timeouts still, but that can be handled by longer timeout where it matters, I hope). But I am not holding my breath. Many tests failed due to timeout (see the excerpt from the log at the end.). I have not analyzed much yet. And based on my previous experience, I think the full test runs for like 2 days. Yes DAYS (not hours). I have no idea what else has changed in M-C/C-C to make this possible. But this is a great start. The results from the first several tests. The whole mochitest is still running. Output from ```egrep "(Subtests passed|Running on|/mach)" t9.list ``` (<- t9.list contains a partial log from the valgrind run). ``` time /NREF-COMM-CENTRAL/mozilla/mach --log-no-times mochitest --valgrind valgrind --valgrind-args='--trace-children=yes --max-threads=5000 --max-stackframe=16000000 --num-transtab-sectors=24 --tool=memcheck --freelist-vol=500000000 --redzone-size=128 --px-default=allregs-at-mem-access --px-file-backed=unwindregs-at-mem-access --malloc-fill=0xA5 --free-fill=0xC3 --num-callers=50 --suppressions=/home/ishikawa/Dropbox/myown.sup --show-mismatched-frees=no --show-possibly-lost=no --read-inline-info=yes --fair-sched=yes --smc-check=all-non-file --gen-suppressions=all -v --trace-signals=yes --vex-iropt-register-updates=allregs-at-mem-access --child-silent-after-fork=yes --suppressions=/home/ishikawa/Dropbox/myown.sup --trace-children-skip=/usr/bin/lsb_release,/usr/bin/hg,/bin/rm,*/bin/certutil,*/bin/pk12util,*/bin/ssltunnel,*/bin/uname,*/bin/which,*/bin/ps,*/bin/grep,*/bin/java,*/fix-stacks,*/firefox/firefox,*/bin/firefox-esr,*/bin/python,*/bin/python2,*/bin/python3,*/bin/python2.7,*/bin/bash,*/bin/nodejs,*/bin/node,*/bin/xpcshell,python3' $* 0:01.78 INFO ishikawa 447031 446969 75 09:22 pts/4 00:00:21 python3 /NREF-COMM-CENTRAL/mozilla/mach --log-no-times mochitest --valgrind valgrind --valgrind-args=--trace-children=yes --max-threads=5000 --max-stackframe=16000000 --num-transtab-sectors=24 --tool=memcheck --freelist-vol=500000000 --redzone-size=128 --px-default=allregs-at-mem-access --px-file-backed=unwindregs-at-mem-access --malloc-fill=0xA5 --free-fill=0xC3 --num-callers=50 --suppressions=/home/ishikawa/Dropbox/myown.sup --show-mismatched-frees=no --show-possibly-lost=no --read-inline-info=yes --fair-sched=yes --smc-check=all-non-file --gen-suppressions=all -v --trace-signals=yes --vex-iropt-register-updates=allregs-at-mem-access --child-silent-after-fork=yes --suppressions=/home/ishikawa/Dropbox/myown.sup --trace-children-skip=/usr/bin/lsb_release,/usr/bin/hg,/bin/rm,*/bin/certutil,*/bin/pk12util,*/bin/ssltunnel,*/bin/uname,*/bin/which,*/bin/ps,*/bin/grep,*/bin/java,*/fix-stacks,*/firefox/firefox,*/bin/firefox-esr,*/bin/python,*/bin/python2,*/bin/python3,*/bin/python2.7,*/bin/bash,*/bin/nodejs,*/bin/node,*/bin/xpcshell,python3 0:01.83 INFO ishikawa 447031 446969 75 09:22 pts/4 00:00:21 python3 /NREF-COMM-CENTRAL/mozilla/mach --log-no-times mochitest --valgrind valgrind --valgrind-args=--trace-children=yes --max-threads=5000 --max-stackframe=16000000 --num-transtab-sectors=24 --tool=memcheck --freelist-vol=500000000 --redzone-size=128 --px-default=allregs-at-mem-access --px-file-backed=unwindregs-at-mem-access --malloc-fill=0xA5 --free-fill=0xC3 --num-callers=50 --suppressions=/home/ishikawa/Dropbox/myown.sup --show-mismatched-frees=no --show-possibly-lost=no --read-inline-info=yes --fair-sched=yes --smc-check=all-non-file --gen-suppressions=all -v --trace-signals=yes --vex-iropt-register-updates=allregs-at-mem-access --child-silent-after-fork=yes --suppressions=/home/ishikawa/Dropbox/myown.sup --trace-children-skip=/usr/bin/lsb_release,/usr/bin/hg,/bin/rm,*/bin/certutil,*/bin/pk12util,*/bin/ssltunnel,*/bin/uname,*/bin/which,*/bin/ps,*/bin/grep,*/bin/java,*/fix-stacks,*/firefox/firefox,*/bin/firefox-esr,*/bin/python,*/bin/python2,*/bin/python3,*/bin/python2.7,*/bin/bash,*/bin/nodejs,*/bin/node,*/bin/xpcshell,python3 0:02.43 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 20:33.55 INFO ishikawa 447031 446969 3 09:22 pts/4 00:00:48 python3 /NREF-COMM-CENTRAL/mozilla/mach --log-no-times mochitest --valgrind valgrind --valgrind-args=--trace-children=yes --max-threads=5000 --max-stackframe=16000000 --num-transtab-sectors=24 --tool=memcheck --freelist-vol=500000000 --redzone-size=128 --px-default=allregs-at-mem-access --px-file-backed=unwindregs-at-mem-access --malloc-fill=0xA5 --free-fill=0xC3 --num-callers=50 --suppressions=/home/ishikawa/Dropbox/myown.sup --show-mismatched-frees=no --show-possibly-lost=no --read-inline-info=yes --fair-sched=yes --smc-check=all-non-file --gen-suppressions=all -v --trace-signals=yes --vex-iropt-register-updates=allregs-at-mem-access --child-silent-after-fork=yes --suppressions=/home/ishikawa/Dropbox/myown.sup --trace-children-skip=/usr/bin/lsb_release,/usr/bin/hg,/bin/rm,*/bin/certutil,*/bin/pk12util,*/bin/ssltunnel,*/bin/uname,*/bin/which,*/bin/ps,*/bin/grep,*/bin/java,*/fix-stacks,*/firefox/firefox,*/bin/firefox-esr,*/bin/python,*/bin/python2,*/bin/python3,*/bin/python2.7,*/bin/bash,*/bin/nodejs,*/bin/node,*/bin/xpcshell,python3 20:33.60 INFO ishikawa 447031 446969 3 09:22 pts/4 00:00:48 python3 /NREF-COMM-CENTRAL/mozilla/mach --log-no-times mochitest --valgrind valgrind --valgrind-args=--trace-children=yes --max-threads=5000 --max-stackframe=16000000 --num-transtab-sectors=24 --tool=memcheck --freelist-vol=500000000 --redzone-size=128 --px-default=allregs-at-mem-access --px-file-backed=unwindregs-at-mem-access --malloc-fill=0xA5 --free-fill=0xC3 --num-callers=50 --suppressions=/home/ishikawa/Dropbox/myown.sup --show-mismatched-frees=no --show-possibly-lost=no --read-inline-info=yes --fair-sched=yes --smc-check=all-non-file --gen-suppressions=all -v --trace-signals=yes --vex-iropt-register-updates=allregs-at-mem-access --child-silent-after-fork=yes --suppressions=/home/ishikawa/Dropbox/myown.sup --trace-children-skip=/usr/bin/lsb_release,/usr/bin/hg,/bin/rm,*/bin/certutil,*/bin/pk12util,*/bin/ssltunnel,*/bin/uname,*/bin/which,*/bin/ps,*/bin/grep,*/bin/java,*/fix-stacks,*/firefox/firefox,*/bin/firefox-esr,*/bin/python,*/bin/python2,*/bin/python3,*/bin/python2.7,*/bin/bash,*/bin/nodejs,*/bin/node,*/bin/xpcshell,python3 20:34.24 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 34:11.90 TEST_END: Test OK. Subtests passed 13/16. Unexpected 3 39:40.61 TEST_END: Test OK. Subtests passed 31/35. Unexpected 1 41:05.25 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 57:59.68 TEST_END: Test OK. Subtests passed 6/8. Unexpected 2 61:36.10 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 77:41.40 TEST_END: Test OK. Subtests passed 4/6. Unexpected 2 80:54.94 TEST_END: Test OK. Subtests passed 3/6. Unexpected 3 82:07.06 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 95:26.38 TEST_END: Test OK. Subtests passed 1/2. Unexpected 1 102:38.05 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 117:17.64 TEST_END: Test OK. Subtests passed 1/2. Unexpected 1 121:19.88 TEST_END: Test OK. Subtests passed 37/39. Unexpected 2 123:09.01 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 140:31.91 TEST_END: Test OK. Subtests passed 31/33. Unexpected 2 142:55.68 TEST_END: Test OK. Subtests passed 21/24. Unexpected 3 143:39.95 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 158:58.01 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1 161:33.68 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1 164:11.30 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 180:17.64 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1 182:25.29 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1 184:42.15 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 199:52.37 TEST_END: Test OK. Subtests passed 3/5. Unexpected 2 203:39.01 TEST_END: Test OK. Subtests passed 3/6. Unexpected 3 205:13.07 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. ``` I forgot exactly where this 2960 is set. Maybe it is default of |mach| when it invokes valgrind(?). Or it may be possible I have applied a local patch to increase this number already. But as in previous comment, (comment 26), I have not increased the timeout in marionette.py before until today. (Come to think of it, I only looked at scripts under mozilla/comm directory and missed this timeout value in marionette.py which is mozilla/testing/marionette/client/marionette_driver/marionette.py) The mochitest is still running slowly, but I have changed the timeout in marionette.py from 1800 to 2400 and will see how the test failures will diminish. A cautious great news so that more memory-related issues can be found for TB by running it under valgrind during mochitest. (Somehow TB under valgrind has run successfully since early this year for xpcshell tests already.) I will summarize what needs to be done to run TB successfully under valgrind (especially the timeout value changes) once I figure out where other timeout values may need increasing.
Interesting. With the change to the timeout to marionette.py in the previous comment (comment 26) and a slightly different parameters passed to valgrind, it seems that the first few tests in mochitest suite seem to proceed to a point where the calendar test is shown on the screen and proceed very slowly. (there are errors obviously due to timeouts still, but that can be handled by longer timeout where it matters, I hope). But I am not holding my breath. Many tests failed due to timeout (see the excerpt from the log at the end.). I have not analyzed much yet. And based on my previous experience, I think the full test runs for like 2 days. Yes DAYS (not hours). I have no idea what else has changed in M-C/C-C to make this possible. But this is a great start. The results from the first several tests. The whole mochitest is still running. Output from ``` egrep "(Subtests passed|Running on|/mach)" t9.list ``` (<- t9.list contains a partial log from the valgrind run). ``` time /NREF-COMM-CENTRAL/mozilla/mach --log-no-times mochitest --valgrind valgrind --valgrind-args='--trace-children=yes --max-threads=5000 --max-stackframe=16000000 --num-transtab-sectors=24 --tool=memcheck --freelist-vol=500000000 --redzone-size=128 --px-default=allregs-at-mem-access --px-file-backed=unwindregs-at-mem-access --malloc-fill=0xA5 --free-fill=0xC3 --num-callers=50 --suppressions=/home/ishikawa/Dropbox/myown.sup --show-mismatched-frees=no --show-possibly-lost=no --read-inline-info=yes --fair-sched=yes --smc-check=all-non-file --gen-suppressions=all -v --trace-signals=yes --vex-iropt-register-updates=allregs-at-mem-access --child-silent-after-fork=yes --suppressions=/home/ishikawa/Dropbox/myown.sup --trace-children-skip=/usr/bin/lsb_release,/usr/bin/hg,/bin/rm,*/bin/certutil,*/bin/pk12util,*/bin/ssltunnel,*/bin/uname,*/bin/which,*/bin/ps,*/bin/grep,*/bin/java,*/fix-stacks,*/firefox/firefox,*/bin/firefox-esr,*/bin/python,*/bin/python2,*/bin/python3,*/bin/python2.7,*/bin/bash,*/bin/nodejs,*/bin/node,*/bin/xpcshell,python3' $* 0:01.78 INFO ishikawa 447031 446969 75 09:22 pts/4 00:00:21 python3 /NREF-COMM-CENTRAL/mozilla/mach --log-no-times mochitest --valgrind valgrind --valgrind-args=--trace-children=yes --max-threads=5000 --max-stackframe=16000000 --num-transtab-sectors=24 --tool=memcheck --freelist-vol=500000000 --redzone-size=128 --px-default=allregs-at-mem-access --px-file-backed=unwindregs-at-mem-access --malloc-fill=0xA5 --free-fill=0xC3 --num-callers=50 --suppressions=/home/ishikawa/Dropbox/myown.sup --show-mismatched-frees=no --show-possibly-lost=no --read-inline-info=yes --fair-sched=yes --smc-check=all-non-file --gen-suppressions=all -v --trace-signals=yes --vex-iropt-register-updates=allregs-at-mem-access --child-silent-after-fork=yes --suppressions=/home/ishikawa/Dropbox/myown.sup --trace-children-skip=/usr/bin/lsb_release,/usr/bin/hg,/bin/rm,*/bin/certutil,*/bin/pk12util,*/bin/ssltunnel,*/bin/uname,*/bin/which,*/bin/ps,*/bin/grep,*/bin/java,*/fix-stacks,*/firefox/firefox,*/bin/firefox-esr,*/bin/python,*/bin/python2,*/bin/python3,*/bin/python2.7,*/bin/bash,*/bin/nodejs,*/bin/node,*/bin/xpcshell,python3 0:01.83 INFO ishikawa 447031 446969 75 09:22 pts/4 00:00:21 python3 /NREF-COMM-CENTRAL/mozilla/mach --log-no-times mochitest --valgrind valgrind --valgrind-args=--trace-children=yes --max-threads=5000 --max-stackframe=16000000 --num-transtab-sectors=24 --tool=memcheck --freelist-vol=500000000 --redzone-size=128 --px-default=allregs-at-mem-access --px-file-backed=unwindregs-at-mem-access --malloc-fill=0xA5 --free-fill=0xC3 --num-callers=50 --suppressions=/home/ishikawa/Dropbox/myown.sup --show-mismatched-frees=no --show-possibly-lost=no --read-inline-info=yes --fair-sched=yes --smc-check=all-non-file --gen-suppressions=all -v --trace-signals=yes --vex-iropt-register-updates=allregs-at-mem-access --child-silent-after-fork=yes --suppressions=/home/ishikawa/Dropbox/myown.sup --trace-children-skip=/usr/bin/lsb_release,/usr/bin/hg,/bin/rm,*/bin/certutil,*/bin/pk12util,*/bin/ssltunnel,*/bin/uname,*/bin/which,*/bin/ps,*/bin/grep,*/bin/java,*/fix-stacks,*/firefox/firefox,*/bin/firefox-esr,*/bin/python,*/bin/python2,*/bin/python3,*/bin/python2.7,*/bin/bash,*/bin/nodejs,*/bin/node,*/bin/xpcshell,python3 0:02.43 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 20:33.55 INFO ishikawa 447031 446969 3 09:22 pts/4 00:00:48 python3 /NREF-COMM-CENTRAL/mozilla/mach --log-no-times mochitest --valgrind valgrind --valgrind-args=--trace-children=yes --max-threads=5000 --max-stackframe=16000000 --num-transtab-sectors=24 --tool=memcheck --freelist-vol=500000000 --redzone-size=128 --px-default=allregs-at-mem-access --px-file-backed=unwindregs-at-mem-access --malloc-fill=0xA5 --free-fill=0xC3 --num-callers=50 --suppressions=/home/ishikawa/Dropbox/myown.sup --show-mismatched-frees=no --show-possibly-lost=no --read-inline-info=yes --fair-sched=yes --smc-check=all-non-file --gen-suppressions=all -v --trace-signals=yes --vex-iropt-register-updates=allregs-at-mem-access --child-silent-after-fork=yes --suppressions=/home/ishikawa/Dropbox/myown.sup --trace-children-skip=/usr/bin/lsb_release,/usr/bin/hg,/bin/rm,*/bin/certutil,*/bin/pk12util,*/bin/ssltunnel,*/bin/uname,*/bin/which,*/bin/ps,*/bin/grep,*/bin/java,*/fix-stacks,*/firefox/firefox,*/bin/firefox-esr,*/bin/python,*/bin/python2,*/bin/python3,*/bin/python2.7,*/bin/bash,*/bin/nodejs,*/bin/node,*/bin/xpcshell,python3 20:33.60 INFO ishikawa 447031 446969 3 09:22 pts/4 00:00:48 python3 /NREF-COMM-CENTRAL/mozilla/mach --log-no-times mochitest --valgrind valgrind --valgrind-args=--trace-children=yes --max-threads=5000 --max-stackframe=16000000 --num-transtab-sectors=24 --tool=memcheck --freelist-vol=500000000 --redzone-size=128 --px-default=allregs-at-mem-access --px-file-backed=unwindregs-at-mem-access --malloc-fill=0xA5 --free-fill=0xC3 --num-callers=50 --suppressions=/home/ishikawa/Dropbox/myown.sup --show-mismatched-frees=no --show-possibly-lost=no --read-inline-info=yes --fair-sched=yes --smc-check=all-non-file --gen-suppressions=all -v --trace-signals=yes --vex-iropt-register-updates=allregs-at-mem-access --child-silent-after-fork=yes --suppressions=/home/ishikawa/Dropbox/myown.sup --trace-children-skip=/usr/bin/lsb_release,/usr/bin/hg,/bin/rm,*/bin/certutil,*/bin/pk12util,*/bin/ssltunnel,*/bin/uname,*/bin/which,*/bin/ps,*/bin/grep,*/bin/java,*/fix-stacks,*/firefox/firefox,*/bin/firefox-esr,*/bin/python,*/bin/python2,*/bin/python3,*/bin/python2.7,*/bin/bash,*/bin/nodejs,*/bin/node,*/bin/xpcshell,python3 20:34.24 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 34:11.90 TEST_END: Test OK. Subtests passed 13/16. Unexpected 3 39:40.61 TEST_END: Test OK. Subtests passed 31/35. Unexpected 1 41:05.25 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 57:59.68 TEST_END: Test OK. Subtests passed 6/8. Unexpected 2 61:36.10 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 77:41.40 TEST_END: Test OK. Subtests passed 4/6. Unexpected 2 80:54.94 TEST_END: Test OK. Subtests passed 3/6. Unexpected 3 82:07.06 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 95:26.38 TEST_END: Test OK. Subtests passed 1/2. Unexpected 1 102:38.05 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 117:17.64 TEST_END: Test OK. Subtests passed 1/2. Unexpected 1 121:19.88 TEST_END: Test OK. Subtests passed 37/39. Unexpected 2 123:09.01 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 140:31.91 TEST_END: Test OK. Subtests passed 31/33. Unexpected 2 142:55.68 TEST_END: Test OK. Subtests passed 21/24. Unexpected 3 143:39.95 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 158:58.01 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1 161:33.68 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1 164:11.30 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 180:17.64 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1 182:25.29 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1 184:42.15 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. 199:52.37 TEST_END: Test OK. Subtests passed 3/5. Unexpected 2 203:39.01 TEST_END: Test OK. Subtests passed 3/6. Unexpected 3 205:13.07 INFO runtests.py | Running on Valgrind. Using timeout of 2960 seconds. ``` I forgot exactly where this 2960 is set. Maybe it is default of |mach| when it invokes valgrind(?). Or it may be possible I have applied a local patch to increase this number already. But as in previous comment, (comment 26), I have not increased the timeout in marionette.py before until today. (Come to think of it, I only looked at scripts under mozilla/comm directory and missed this timeout value in marionette.py which is mozilla/testing/marionette/client/marionette_driver/marionette.py) The mochitest is still running slowly, but I have changed the timeout in marionette.py from 1800 to 2400 and will see how the test failures will diminish. A cautious great news so that more memory-related issues can be found for TB by running it under valgrind during mochitest. (Somehow TB under valgrind has run successfully since early this year for xpcshell tests already.) I will summarize what needs to be done to run TB successfully under valgrind (especially the timeout value changes) once I figure out where other timeout values may need increasing.