(In reply to Magnus Melin [:mkmelin] from comment #143) > (In reply to ISHIKAWA, Chiaki from comment #137) > > Note the "Missing .messageOffset" string. > > The warning lines appear somewhere between 100-200 times during xpcshell test. > > I forgot to mention.: this is an xpcshell test run of FULL DEBUG version under Debian GNU/Linux. > > I checked the treeherder logs, and it's not there. So either some local patch, or something else. Anyway, best to keep it in a separate bug - and see if you can note down which test(s) trigger it. Thank you for the comment. Will file a separate bug for this issue. As for the visibility of warning lines, you have top run xpcshtest with "--serialize --verbose" to see the warnings. Right now, I am seeing them locally. Warnings are not printed from ordinary test run if the test as a whole is deemed to have succeeded. I have not been able to figure out how to run xpctest with "--serialize --verbose" on trreeherder I am beginning to feel maybe the JSON data that seems to configure the job on try-comm-central and others can be tweaked to contain these flags somewhere and then the test runs with these flags.
Bug 1742975 Comment 149 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Magnus Melin [:mkmelin] from comment #143) > (In reply to ISHIKAWA, Chiaki from comment #137) > > Note the "Missing .messageOffset" string. > > The warning lines appear somewhere between 100-200 times during xpcshell test. > > I forgot to mention.: this is an xpcshell test run of FULL DEBUG version under Debian GNU/Linux. > > I checked the treeherder logs, and it's not there. So either some local patch, or something else. Anyway, best to keep it in a separate bug - and see if you can note down which test(s) trigger it. Thank you for the comment. Will file a separate bug for this issue. (Oops. It is --sequential and not --serialize. I was writing from memory. I am fixing the typo.) As for the visibility of warning lines, you have top run xpcshtest with "--sequential --verbose" to see the warnings. Right now, I am seeing them locally. Warnings are not printed from ordinary test run if the test as a whole is deemed to have succeeded. I have not been able to figure out how to run xpctest with "--sequential --verbose" on trreeherder I am beginning to feel maybe the JSON data that seems to configure the job on try-comm-central and others can be tweaked to contain these flags somewhere and then the test runs with these flags.