Open supriyogit opened 11 years ago
On the jenkins server, although the build is successful, I cannot locate the sdk in the out folder (should be under host/platform/sdk). In addition, the console output shows a figure "fail", while the final build result is successful.
Right now the error is because building SDK also builds the emulators, which result in the following errors:
Package symbols: out/target/product/generic/sdk-symbols-eng.supriyo.zip Package SDK: out/host/darwin-x86/sdk/android-sdk_eng.supriyo_mac-x86.zip SDK: warning: including GNU target out/target/product/generic/system/lib/libgccdemangle.so sdk/build/tools.atree:43: couldn't locate source file: bin/emulator sdk/build/tools.atree:44: couldn't locate source file: bin/emulator-x86 sdk/build/tools.atree:45: couldn't locate source file: bin/emulator-arm sdk/build/tools.atree:46: couldn't locate source file: bin/emulator-mips sdk/build/tools.atree:47: couldn't locate source file: bin/emulator64-x86 sdk/build/tools.atree:48: couldn't locate source file: bin/emulator64-arm sdk/build/tools.atree:49: couldn't locate source file: bin/emulator64-mips make: *\ [out/host/darwin-x86/sdk/android-sdk_eng.supriyo_mac-x86.zip] Error 44
Is there any way to disable the build of emulator? And how does this error come out from nowhere...
The error does not come from nowhere. Because you are most likely doing a multithreaded build the tail of log statements is not representative of the error at all. The real error is buried in the full logs. Its part of the reason why I save the full logs on the VM.
You can do also a verbose output from make. You can do make showcommands sdk V=1
. Warning: this will generate ~70MB of log output. It's best to
redirect it like: make showcommands sdk V=1 > build_log 2>&1
...then use
tail -f build_log
to keep track of the build. This make command will show
commands that make
actually does, and in the resulting logs you will find
an exit 44;
bash statement in one of the commands which is the particular
command that is causing the error in the build. Report back with these
details to see if the building of the SDK is something we can fix.
AFAIK, there is no way to build the emulator on OSX. I didn't know this also prevents making the SDK. The only way is to downgrade to snow-leopard and an old version of XCode.
On Tue, Jul 23, 2013 at 4:48 PM, Chenguang Shen notifications@github.comwrote:
Right now the error is because building SDK also builds the emulators, which result in the following errors:
Package symbols: out/target/product/generic/sdk-symbols-eng.supriyo.zip Package SDK: out/host/darwin-x86/sdk/android-sdk_eng.supriyo_mac-x86.zip SDK: warning: including GNU target out/target/product/generic/system/lib/libgccdemangle.so sdk/build/tools.atree:43: couldn't locate source file: bin/emulator sdk/build/tools.atree:44: couldn't locate source file: bin/emulator-x86 sdk/build/tools.atree:45: couldn't locate source file: bin/emulator-arm sdk/build/tools.atree:46: couldn't locate source file: bin/emulator-mips sdk/build/tools.atree:47: couldn't locate source file: bin/emulator64-x86 sdk/build/tools.atree:48: couldn't locate source file: bin/emulator64-arm sdk/build/tools.atree:49: couldn't locate source file: bin/emulator64-mips make: *\ [out/host/darwin-x86/sdk/android-sdk_eng.supriyo_mac-x86.zip] Error 44
Is there any way to disable the build of emulator? And how does this error come out from nowhere...
— Reply to this email directly or view it on GitHubhttps://github.com/nesl/platform_frameworks_native/issues/8#issuecomment-21444862 .
It looks like "Build 47" on the VM had a lunch sdk-eng
command but did
not subsequently do a make sdk
so it looks like the sdk was not
packaged. Ideally you'll want to set the lunch
paramter to sdk-eng
and
also check make sdk
Also...looking at the script that actually processes the parameters entered
on the jenkins website, the "make sdk" checkbox is actually a noop, i.e.
not implemented yet. I've added it on now, and it should actually do a
make sdk
I'm going to cancel "Build 48" since the wrong parameters are set, and start a new build.
On Tue, Jul 23, 2013 at 7:35 PM, Kasturi Raghavan kasturir@g.ucla.eduwrote:
The error does not come from nowhere. Because you are most likely doing a multithreaded build the tail of log statements is not representative of the error at all. The real error is buried in the full logs. Its part of the reason why I save the full logs on the VM.
You can do also a verbose output from make. You can do
make showcommands sdk V=1
. Warning: this will generate ~70MB of log output. It's best to redirect it like:make showcommands sdk V=1 > build_log 2>&1
...then usetail -f build_log
to keep track of the build. This make command will show commands thatmake
actually does, and in the resulting logs you will find anexit 44;
bash statement in one of the commands which is the particular command that is causing the error in the build. Report back with these details to see if the building of the SDK is something we can fix.AFAIK, there is no way to build the emulator on OSX. I didn't know this also prevents making the SDK. The only way is to downgrade to snow-leopard and an old version of XCode.
On Tue, Jul 23, 2013 at 4:48 PM, Chenguang Shen notifications@github.comwrote:
Right now the error is because building SDK also builds the emulators, which result in the following errors:
Package symbols: out/target/product/generic/sdk-symbols-eng.supriyo.zip Package SDK: out/host/darwin-x86/sdk/android-sdk_eng.supriyo_mac-x86.zip SDK: warning: including GNU target out/target/product/generic/system/lib/libgccdemangle.so sdk/build/tools.atree:43: couldn't locate source file: bin/emulator sdk/build/tools.atree:44: couldn't locate source file: bin/emulator-x86 sdk/build/tools.atree:45: couldn't locate source file: bin/emulator-arm sdk/build/tools.atree:46: couldn't locate source file: bin/emulator-mips sdk/build/tools.atree:47: couldn't locate source file: bin/emulator64-x86 sdk/build/tools.atree:48: couldn't locate source file: bin/emulator64-arm sdk/build/tools.atree:49: couldn't locate source file: bin/emulator64-mips make: *\ [out/host/darwin-x86/sdk/android-sdk_eng.supriyo_mac-x86.zip] Error 44
Is there any way to disable the build of emulator? And how does this error come out from nowhere...
— Reply to this email directly or view it on GitHubhttps://github.com/nesl/platform_frameworks_native/issues/8#issuecomment-21444862 .
I see. That's probably why build #46 succeeded but did not generate the sdk. Thanks for pointing this out.
Should be actually doing a make sdk now: http://android.0x72.com:8080/job/android-jb-privacy/49/console
On Tue, Jul 23, 2013 at 7:44 PM, Chenguang Shen notifications@github.comwrote:
I see. That's probably why build #46 succeeded but did not generate the sdk. Thanks for pointing this out.
— Reply to this email directly or view it on GitHubhttps://github.com/nesl/platform_frameworks_native/issues/8#issuecomment-21454503 .
Restarted build after VM reboot :/ http://android.0x72.com:8080/job/android-jb-privacy/54/console
Build 55 is successful but /aosp/jenkins_home/jobs/android-jb-privacy/workspace/copy/android-jb-privacy-github_jb-privacy-55/out/target/product/generic/sdk directory does not have the sdk.
Looks like there is a still issue and it was not actually successful... not sure why the build job says it succeeded!
make: *\ [out/target/common/docs/ds-timestamp] Error 45
On Wed, Jul 24, 2013 at 6:16 AM, supriyogit notifications@github.comwrote:
Build 55 is successful but
/aosp/jenkins_home/jobs/android-jb-privacy/workspace/copy/android-jb-privacy-github_jb-privacy-55/out/target/product/generic/sdk directory does not have the sdk.
— Reply to this email directly or view it on GitHubhttps://github.com/nesl/platform_frameworks_native/issues/8#issuecomment-21475563 .
I'm rebuilding with the showcommands V=1
command to debug. I can't
actually look at this till after work though.
On Wed, Jul 24, 2013 at 1:37 PM, Kasturi Raghavan kasturir@g.ucla.eduwrote:
Looks like there is a still issue and it was not actually successful... not sure why the build job says it succeeded!
make: *\ [out/target/common/docs/ds-timestamp] Error 45
On Wed, Jul 24, 2013 at 6:16 AM, supriyogit notifications@github.comwrote:
Build 55 is successful but
/aosp/jenkins_home/jobs/android-jb-privacy/workspace/copy/android-jb-privacy-github_jb-privacy-55/out/target/product/generic/sdk directory does not have the sdk.
— Reply to this email directly or view it on GitHubhttps://github.com/nesl/platform_frameworks_native/issues/8#issuecomment-21475563 .
Kasturi, does the nesl android_jenkins repo have the latest change? I'm thinking about setting up a more powerful VM for jenkins.
In the log of build #56, the error is shown as: out/host/linux-x86/bin/acp -fp 1 sdk/monitor/monitor out/host/linux-x86/obj/EXECUTABLES/monitor_intermediates/monitor acp: destination directory 'out/host/linux-x86/obj/EXECUTABLES/monitor_intermediates/monitor' does not exist make: *\ [out/host/linux-x86/obj/EXECUTABLES/monitor_intermediates/monitor] Error 1
The scripts on github are probably a few days old. You can add latest /aosp/bin/*.sh into the github repo.
On Wed, Jul 24, 2013 at 2:19 PM, Chenguang Shen notifications@github.comwrote:
Kasturi, does the nesl android_jenkins repo have the latest change? I'm thinking about setting up a more powerful VM for jenkins.
— Reply to this email directly or view it on GitHubhttps://github.com/nesl/platform_frameworks_native/issues/8#issuecomment-21504989 .
About the build problem: maybe you have to do a make
then a make sdk
?
I'm doing that now, lets see if it does something...
On Wed, Jul 24, 2013 at 2:55 PM, Kasturi Raghavan kasturir@g.ucla.eduwrote:
The scripts on github are probably a few days old. You can add latest /aosp/bin/*.sh into the github repo.
On Wed, Jul 24, 2013 at 2:19 PM, Chenguang Shen notifications@github.comwrote:
Kasturi, does the nesl android_jenkins repo have the latest change? I'm thinking about setting up a more powerful VM for jenkins.
— Reply to this email directly or view it on GitHubhttps://github.com/nesl/platform_frameworks_native/issues/8#issuecomment-21504989 .
Do we need to do a full build and then a make sdk?? I tried a couple of things on the mac too..but no success as yet. I will check the logs on the recent build on jenkins.
On Jul 24, 2013, at 12:19 PM, 6b72 wrote:
About the build problem: maybe you have to do a
make
then amake sdk
?I'm doing that now, lets see if it does something...
On Wed, Jul 24, 2013 at 2:55 PM, Kasturi Raghavan kasturir@g.ucla.eduwrote:
The scripts on github are probably a few days old. You can add latest /aosp/bin/*.sh into the github repo.
On Wed, Jul 24, 2013 at 2:19 PM, Chenguang Shen notifications@github.comwrote:
Kasturi, does the nesl android_jenkins repo have the latest change? I'm thinking about setting up a more powerful VM for jenkins.
— Reply to this email directly or view it on GitHubhttps://github.com/nesl/platform_frameworks_native/issues/8#issuecomment-21504989 .
— Reply to this email directly or view it on GitHub.
Some success at last. On the Mac I did the following and am getting a successful sdk
In sdk/build/tools.atree commented out the lines which were including the emulator files. And did a make sdk. It worked.
I have been able to get the sdk to work on eclipse.
Regards Supriyo
On Jul 24, 2013, at 12:19 PM, 6b72 wrote:
About the build problem: maybe you have to do a
make
then amake sdk
?I'm doing that now, lets see if it does something...
On Wed, Jul 24, 2013 at 2:55 PM, Kasturi Raghavan kasturir@g.ucla.eduwrote:
The scripts on github are probably a few days old. You can add latest /aosp/bin/*.sh into the github repo.
On Wed, Jul 24, 2013 at 2:19 PM, Chenguang Shen notifications@github.comwrote:
Kasturi, does the nesl android_jenkins repo have the latest change? I'm thinking about setting up a more powerful VM for jenkins.
— Reply to this email directly or view it on GitHubhttps://github.com/nesl/platform_frameworks_native/issues/8#issuecomment-21504989 .
— Reply to this email directly or view it on GitHub.
looks like the DONE/FAIL message at the end of the build on the VM are broken.
Looks like the latest build did finally produce a sdk zip! http://android.0x72.com:8080/job/android-jb-privacy/ws/copy/android-jb-privacy-github_jb-privacy-63/out/host/linux-x86/sdk/
On Wed, Jul 24, 2013 at 7:20 PM, supriyogit notifications@github.comwrote:
Some success at last. On the Mac I did the following and am getting a successful sdk
In sdk/build/tools.atree commented out the lines which were including the emulator files. And did a make sdk. It worked.
I have been able to get the sdk to work on eclipse.
Regards Supriyo
On Jul 24, 2013, at 12:19 PM, 6b72 wrote:
About the build problem: maybe you have to do a
make
then amake sdk
?I'm doing that now, lets see if it does something...
On Wed, Jul 24, 2013 at 2:55 PM, Kasturi Raghavan kasturir@g.ucla.eduwrote:
The scripts on github are probably a few days old. You can add latest /aosp/bin/*.sh into the github repo.
On Wed, Jul 24, 2013 at 2:19 PM, Chenguang Shen < notifications@github.com>wrote:
Kasturi, does the nesl android_jenkins repo have the latest change? I'm thinking about setting up a more powerful VM for jenkins.
— Reply to this email directly or view it on GitHub< https://github.com/nesl/platform_frameworks_native/issues/8#issuecomment-21504989>
.
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHubhttps://github.com/nesl/platform_frameworks_native/issues/8#issuecomment-21523530 .
Cool! Did you change any code/makefile? Or we just need a full build before making sdk.
No code changes needed...
Look at the current script to make...or the console log for the the sequence of commands that seem to work...
I should do a full rebuild from scratch to confirm.
-k
On Jul 25, 2013, at 1:47 PM, Chenguang Shen notifications@github.com wrote:
Cool! Did you change any code/makefile? Or we just need a full build before making sdk.
— Reply to this email directly or view it on GitHubhttps://github.com/nesl/platform_frameworks_native/issues/8#issuecomment-21571403 .
Checking build tools versions... build/core/main.mk:165: **** build/core/main.mk:166: * gcc is linked to llvm-gcc which will build/core/main.mk:167: * not create a useable emulator. build/core/main.mk:168: ****