On 2015/12/05 21:09, Stefan Sitter wrote:
On 04.12.2015 13:16, ishikawa wrote:
I suspect then the C-C tree was in a confused state in the first few
days of December.
...
So I think the tree is in a better shape now.
In advance to refreshing your source tree you can take a look at
<https://treeherder.mozilla.org/#/jobs?repo=comm-central>. This page
give you information if comm-central builds are successfully
compiling or if there are build failures.
Thank you for the pointers.
Let me explain what was going on at the beginning of December.
Step 1:
I had to refresh M-C portion of the C-C source tree anyway because
the TB try submission seems to incorporate the latest M-C changes always
(this is noticeable by the included M-C patches in one's try submission):
These change often break C-C tree and did break C-C TB build at the
beginning of December.
I had to incorporate the M-C changes to see what is breaking the build
and test.
Then C-C tree needs to be changed to fix these breaks caused by M-C changes.
This means that I have to fetch the latest C-C tree in such a case, and
sure enough C-C tree was modified to fix the break caused by change in
M-C tree.
Step 2:
So I have to fetch the latest C-C + M-C tree changes to compile C-C TB
both locally and on tryserver.
TB build was made to work on local PC.
Unfortunately, the frantic pace of M-C changes brought about
new set of changes in M-C tree, and some of these new patches began causing
strange build errors on tryserver already. Go to step 1.
This cycle repeated for at least three times due to new build failures
introduced back to back due to the changes in M-C tree.
Under these circumstances, a poor patch contributor who needs to test
his/her patches on a hardware platform that he/she does not own needs
to make his/her tryserver submission succeed even if it means
a strange and temporal tweak or kludge of one's local tree.
(And overcoming thefailures on tryserver in a creative manner.)
Otherwise, the patch cannot be tested for at least a few days on the
hardware platforms which he/she does not own.
That was what I was trying to perform when I found out the issue of
"No preprocessor directives found" error.
I think eventually I had to wait for about a week before anything
sensible could be gleaned from bisecting patches at the beginning of
December.
A very painful wait. Tough luck.
Of course, nobody promised a rose garden when I began submitting patches
to TB :-)
TIA
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
