Dan Willemsen於 2016年8月27日星期六 UTC+8上午12時51分26秒寫道：
>
> If you run:
>
> $ (cd bootable/recovery/tests ; find -L testdata/*)
>
> multiple times, does it give you the results in different orders? Does it
> return different results before and after a build?
>
It always gives the same results.
If not, I'm surprised since nobody change
any file in bootable/recovery/tests.
find does return results in filesystem order, which is not defined. This
> hasn't been a problem with any filesystem that I've seen -- you always get
> the same order until something changes in that directory, then the order
> may change.
>
>
There is nothing changed in that directory.
In fact I didn't change anything under
the bootable/recovery/ dir. It's exactly
the same as AOSP.
Am I the only one see this issue?
Actually the problem is not at bootable/recovery/tests.
The problem is the new build system always thinks
something is changed. If I removed this line in
bootable/recovery/tests/Android.mk
testdata_files := $(call find-subdir-files, testdata/*)
and make again, it said
bootable/recovery/tests/Android.mk was modified, regenerating...
This is OK since I did change the makefile.
However make again it said:
$(shell cd libcore && ls -d */src/test/{java,resources} 2> /dev/null) was
changed, regenerating...
(what? I didn't change libcore)
--
--
You received this message because you are subscribed to the "Android Building"
mailing list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
