Bugzilla

C-C TB xpcshell-tests only print out stdout/stderr output when the test fails.
This means many errors/warnings that don't somehow affect the outcome of each xcpshell tests do not get proper attention.

By passing |--verbose| option to |mach xpcshell-tests|, we can force the listing of stdout/stderr output.

This output  was necessary for me to check for memory-related issues by running C-C TB (full debug version) during |mach xpcshell-tests --verbose|.
This is because valgrind warnings go into stderr (?) output.

So I ran |xpcshell-tests| under valgrind to find out what warnings if any from valgrind appears.

There *WERE* many valgrind warnings pointing to uninitialized memory access.
Not only that, I was staggered to find so many JavaScript strict warnings and Java warnings in the dumped listing.

So I create this meta entry to keep track of the issues found during the execution of |mach xpcshell-tests --verbose| under valgrind on a local PC that runs linux 64-bit.
I believe most of the errors found are universal across different architectures, though.
That is why I set platform and OS to all each.

I am going to file initially the general list of issues:
- java strict warnings
- java warnings
- valgrind violations
   found in the test of  M-C portion (not tested extensively due to the large volume of output produced. 110+ MB )
   found in the test of  C-C portion.

In this bugzilla, I am going to upload the summary of errors/warnings found.
Each error/warning shall be addressed by a separate bugzilla entry.

C-C TB xpcshell-tests only print out stdout/stderr output when the test fails.
This means many errors/warnings that don't somehow affect the outcome of each xcpshell tests do not get proper attention.

By passing |--verbose| option to |mach xpcshell-tests|, we can force the listing of stdout/stderr output.

This output  was necessary for me to check for memory-related issues by running C-C TB (full debug version) during |mach xpcshell-tests --verbose|.
This is because valgrind warnings go into stderr (?) output.

So I ran |xpcshell-tests  --verbose| under valgrind to find out what warnings if any from valgrind appears.

There *WERE* many valgrind warnings pointing to uninitialized memory access.
Not only that, I was staggered to find so many JavaScript strict warnings and JavaScript warnings in the dumped listing.

So I create this meta entry to keep track of the issues found during the execution of |mach xpcshell-tests --verbose| under valgrind on a local PC that runs linux 64-bit.
I believe most of the errors found are universal across different architectures, though.
That is why I set platform and OS to all each.

I am going to file initially the general list of issues:
- java strict warnings
- java warnings
- valgrind violations
   found in the test of  M-C portion (not tested extensively due to the large volume of output produced. 110+ MB )
   found in the test of  C-C portion.

In this bugzilla, I am going to upload the summary of errors/warnings found.
Each error/warning shall be addressed by a separate bugzilla entry.