When I see such infrastructure-related errors, anything in the log is suspect.
I can't rely on the content of the log. An error reported may not be due to
the bug in the code, but
could be a tryserver infrastructure problem.
In order to see if it is not only me, I looked at other people's jobs, and
sure enough, I found a job
from someone else whose mozmill test log shows the same set of errors.
There click on the colorful (red/violet?) [Z] icons and you will see errors
at the beginning.
Somehow orange [Z] for windows mozmill test does not show the particular set
of errors, but
Windows 7 opt mozmill test log shows
the failure of C:\slave\test\build\tests\mozmill\testBasicFunctionality
which suggests to me that something went awry under windows opt test, too.
Has anyone experienced this issue aside from me and that particular job's
I am afraid this really gets in the way of using tryserver effectively to
test C-C TB on platforms that I do not own.
I run linux 64-bit locally, but I do need to test windows and OSX versions.
I also need to compare the run on my PC and one on the tryserver to make
sure if the
problems I see locally are permanent and not transient ones. Seeing errors
both locally and remotely
gives me high assurance that the problems are permanent ones.