Change the order of include pathes to avoid including potential staled files.

Change the order of include pathes to avoid including potential staled files.

BUG=380054
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=175728

[dcheng, 2014-06-06 22:11:56]

rslgtm if it doesn't break any builders and incremental build after applying
FastMobileScrolling works. Sorry for the trouble.

[c.shu, 2014-06-06 22:23:04]

On 2014/06/06 22:11:56, dcheng wrote:
> rslgtm if it doesn't break any builders and incremental build after applying
> FastMobileScrolling works. Sorry for the trouble.

Thanks, dcheng. To do the test, I manually *copied* all generated files under
core, modules, and platforms back to gen/blink. Then I applied the
FastMobileScrolling patch. The build went through fine. I am checking the commit
flag now.

[c.shu, 2014-06-06 22:23:13]

The CQ bit was checked by c.shu@samsung.com

[commit-bot: I haz the power, 2014-06-06 22:24:50]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/c.shu@samsung.com/325483002/1

[commit-bot: I haz the power, 2014-06-06 23:38:08]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  linux_blink_dbg on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/linux_blink_dbg/builds/1...)
  linux_blink_rel on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/linux_blink_rel/builds/1...)
  mac_blink_rel on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/mac_blink_rel/builds/10686)
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/14084)

[commit-bot: I haz the power, 2014-06-06 23:49:02]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-06-06 23:49:02]

Try jobs failed on following builders:
  mac_blink_rel on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/mac_blink_rel/builds/10699)

[c.shu, 2014-06-07 00:16:23]

The CQ bit was checked by c.shu@samsung.com

[c.shu, 2014-06-07 00:16:57]

On 2014/06/06 23:49:02, I haz the power (commit-bot) wrote:
> Try jobs failed on following builders:
>   mac_blink_rel on tryserver.blink
>
(http://build.chromium.org/p/tryserver.blink/builders/mac_blink_rel/builds/10699)

The test failures should not be related to this CL.

[commit-bot: I haz the power, 2014-06-07 00:17:00]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/c.shu@samsung.com/325483002/1

[haraken, 2014-06-07 02:16:47]

> to avoid including potential staled files.

Just help me understand: In what situation can this happen, specifically?

[commit-bot: I haz the power, 2014-06-07 03:39:22]

Change committed as 175728

[c.shu, 2014-06-07 15:22:59]

On 2014/06/07 02:16:47, haraken wrote:
> > to avoid including potential staled files.
> 
> Just help me understand: In what situation can this happen, specifically?

Hi, haraken, here's the full story.
1. Originally, all generated files are located under gen/blink. E.g.,
HTMLNames.h
and cpp files include it using
"#include "HTMLNames.h"
since gen/blink is in the include search path.
2. The CL that moves the generated files to their component's directory changed
the location.
E.g., HTMLNames.h is generated under gen/blink/core. The cpp file still uses
"#include "HTMLNames.h"
because gen/blink/core is added in the include search path.
But if you don't do a clean build after this CL, the gen/blink/HTMLNames.h still
exists in your output dir.
And gen/blink is also in the search path (for including v8 files).
If "gen/blink" is found first, the staled gen/blink/HTMLNames.h is used.
This will cause problem only if HTMLNames.h is regenerated with different
content.
Some people have reported the problem and it also happened to my own CL related
to fastmobilescrolling flag.
3. This CL changes the order of search paths, so gen/blink/core is found before
gen/blink and the staled files are ignore.
Thanks.

[haraken, 2014-06-07 16:32:35]

On 2014/06/07 15:22:59, c.shu wrote:
> On 2014/06/07 02:16:47, haraken wrote:
> > > to avoid including potential staled files.
> > 
> > Just help me understand: In what situation can this happen, specifically?
> 
> Hi, haraken, here's the full story.
> 1. Originally, all generated files are located under gen/blink. E.g.,
> HTMLNames.h
> and cpp files include it using
> "#include "HTMLNames.h"
> since gen/blink is in the include search path.
> 2. The CL that moves the generated files to their component's directory
changed
> the location.
> E.g., HTMLNames.h is generated under gen/blink/core. The cpp file still uses
> "#include "HTMLNames.h"
> because gen/blink/core is added in the include search path.
> But if you don't do a clean build after this CL, the gen/blink/HTMLNames.h
still
> exists in your output dir.
> And gen/blink is also in the search path (for including v8 files).
> If "gen/blink" is found first, the staled gen/blink/HTMLNames.h is used.
> This will cause problem only if HTMLNames.h is regenerated with different
> content.
> Some people have reported the problem and it also happened to my own CL
related
> to fastmobilescrolling flag.
> 3. This CL changes the order of search paths, so gen/blink/core is found
before
> gen/blink and the staled files are ignore.
> Thanks.

ah, got it; thanks for the clarification. LGTM.