[dev] 1.3-rel Branch out/QA start request.

[Soemin Tjong]

at lists.iotivity.org>

Subject: Re: [dev] 1.3-rel Branch out/QA start request.



On 04/10/2017 04:57 AM, ??? (Uze Choi) wrote:

> Hi All,

>

>

>

> 1.3-rel branch has been created. 1.3.0 Release period just started.

>

> There are approximately 70 change sets waiting merge on the master

> branches

>

> Except this patches, All code merge should have the release management Lead 
> review +1 on the release branch.





So for owners of waiting changesets... how do we proceed?  The small number I 
have in the queue (five public) I would not consider release-critical, but also 
letting master and 1.3-rel diverge is not wonderful, makes lots of work later 
for someone - I'm remembering what Phil and others had to do to get master back 
in sync with 1.2-rel.



Advice please?







___

iotivity-dev mailing list

iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev=02%7C01%7Ckkane%40microsoft.com%7C3a7057b259e34a700d8608d4805326b6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636274542026472282=kaW7CiPhNlVkyehkZTEnFkQMMNTJXNXUHlkjKaXuMWQ%3D=0






[cid:image001.gif at 01D2B382.BE34AFD0]

[http://ext.samsung.net/mail/ext/v1/external/status/update?userid=uzchoi=bWFpbElEPTIwMTcwNDEwMjI1MDAxZXBjbXMxcDc0NWFkNzAyODE2MThlOTBlMjU3YjJkOTJjYTIyYWRkYyZyZWNpcGllbnRBZGRyZXNzPWtrYW5lQG1pY3Jvc29mdC5jb20_]
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170412/f3bd205e/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13402 bytes
Desc: image001.gif
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170412/f3bd205e/attachment.gif>

[dev] 1.3-rel Branch out/QA start request.

[Bell, Richard S]

___

iotivity-dev mailing list

iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev=02%7C01%7Ckkane%40microsoft.com%7C3a7057b259e34a700d8608d4805326b6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636274542026472282=kaW7CiPhNlVkyehkZTEnFkQMMNTJXNXUHlkjKaXuMWQ%3D=0






[cid:image001.gif at 01D2B36E.59B40470]

[http://ext.samsung.net/mail/ext/v1/external/status/update?userid=uzchoi=bWFpbElEPTIwMTcwNDEwMjI1MDAxZXBjbXMxcDc0NWFkNzAyODE2MThlOTBlMjU3YjJkOTJjYTIyYWRkYyZyZWNpcGllbnRBZGRyZXNzPWtrYW5lQG1pY3Jvc29mdC5jb20_]
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170412/f4f751f8/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13402 bytes
Desc: image001.gif
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170412/f4f751f8/attachment.gif>

[dev] [IoTivity Helpdesk #37305] Unit Test execution issue in Jenkins

[CJ Collier via RT]

Tests are now executing in constrained parallel:

https://gerrit.iotivity.org/gerrit/gitweb?p=ci-management.git;a=blobdiff;f=jjb/iotivity/iotivity-jobs.yaml;h=423c0f35655fabe2e2cb18283dae4751d7e916d2;hp=310105bcc44c6ee0e65776a5869e78604d60bcae;hb=c4e459bcccd011eba47659c22095d81e18781777;hpb=5f305ead96d032344ffce9db4eab8cea9f30ac71

On Mon Feb 27 03:05:47 2017, uzchoi at samsung.com wrote:
> Hi Phil, LF help or anyone else,
> 
> Currently there are frequent unit test build job failure from Jenkins
> verification.
> During Unit Test execution, parallel unit test executing cause racing issue.
> For example, A test case expect A resource server but at the same time B
> test case find A resource first and A resource server close its session.
> Then A test case cannot find A resource.
> https://build.iotivity.org/ci/job/iotivity-verify-unit_tests/10126/
> Test case should have considered this cases but every test case does not
> consider it well.
> 
> As a solution, can we selectively disable this parallel execution for
> specific job(unit test job) or check what is the other issue over there?
> Is it Jenkins system operation responsibility or build script manager
> responsibility or others.
> 
> BR, Uze Choi

[dev] 1.3-rel Branch out/QA start request.

[최우제 (Uze Choi)]

?...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170412/5e5f7fa8/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13402 bytes
Desc: ?? ?? .
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170412/5e5f7fa8/attachment.gif>

[dev] [Android] Linking Notification consumer and Easy Setup service with Android Studio

[Koenraad Verheyden]

Hey all,

I'm designing an app which uses both the Notification consumer and the Easy
Setup service. I'm having some trouble including the necessary libraries.

I'm following the guide on the Wiki: Using IoTivity Base Android API in an
Android Studio Project
<https://wiki.iotivity.org/android_build_instructions#using_iotivity_base_android_api_in_an_android_studio_project>

I built IoTivity for Android and made modules of the created .aar files.

Including the iotivity-base works fine (using OcPlatform etc).
If I add the notification library
(iotivity-x86-notification-service-release.aar) I get the following build
error:

Error:Execution failed for task
':app:transformNativeLibsWithMergeJniLibsForDebug'.
> com.android.build.api.transform.TransformException:
com.android.builder.packaging.DuplicateFileException: Duplicate files
copied in APK
*lib/x86/libocstack-jni.so*

I can fix this error by adding the following to app/build.gradle

packagingOptions {
pickFirst "lib/x86/libocstack-jni.so"
}

With this I can build and deploy the app. But when I call the consumer
service I get the following error:

java.lang.UnsatisfiedLinkError: dlopen failed: library
"./obj/local/x86/libnotification_consumer_wrapper.so" not found

What are the recommended practices including the multiple IoTivity
libraries in an Android Studio project?

With kind regards,
Koenraad
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170412/a4cea750/attachment.html>

[dev] 1.3-rel Branch out/QA start request.

[드와르카]

An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170412/da833b4a/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13402 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170412/da833b4a/attachment.gif>

[dev] 1.3-rel Branch out/QA start request.

[드와르카]

An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170412/c3101508/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13402 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170412/c3101508/attachment.gif>

[dev] 1.3-rel Branch out/QA start request.

[최우제]

HTML ?? ??...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: ?? ?? .
Type: image/gif
Size: 13402 bytes
Desc: ?? ?? .
URL: 

[dev] Android build fails in 1.3-rel branch

[Nash, George]

Jihun Ha,
Give https://gerrit.iotivity.org/gerrit/#/c/18739/ a try it should fix both 
your issues.
George

From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Nash, George
Sent: Tuesday, April 11, 2017 1:23 PM
To: jihun.ha at samsung.com; iotivity-dev at lists.iotivity.org
Subject: Re: [dev] Android build fails in 1.3-rel branch

For the first error the fix is quite easy I have filed a Jira ticket for that 
issue and will have a patch submitted shortly
https://jira.iotivity.org/browse/IOT-2029
I have not been able to reproduce the second issue.
I have seen this type of issue when old build products are causing an error.
Here are two things to try.
1st
Do a clean build
$> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
WITH_CLOUD=1 -c
$> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
WITH_CLOUD=1

If that does not work manually clean the build output and try again sometimes 
the scons clean misses something that should have been cleaned and this solves 
the problem. If you have another build linux or tizen this will wipe out the 
build output for those OS if you may want to be more selective than this. 
Sometimes just deleting the .sconsign.dblite file will fix the issue but I 
normally just rebuild everything.
$> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
WITH_CLOUD=1 ?c
$> rm -fr out #delete the output directory
$> rm .sconsign.dblite #delete scons?s database file that it uses for tracking 
which files need a rebuild.
$> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
WITH_CLOUD=1



From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf 
Of ???
Sent: Tuesday, April 11, 2017 4:46 AM
To: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] Android build fails in 1.3-rel branch


Hi All.



Below problem can be resolved by https://gerrit.iotivity.org/gerrit/#/c/18701/ 
patch.

However, I've encountered other problem as below:



jhha85:~/workspace/iotivity$ scons TARGET_OS=android 
TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 WITH_CLOUD=1
scons: Reading SConscript files ...
HEAD is now at acf202a Fix stack corruption due to calling convention mismatch
linux2
Creating ANDROID_HOME for Android SDK
ANDROID_HOME = 
/home/jhha85/workspace/iotivity/extlibs/android/sdk/android-sdk-linux

*** Info **
*Android NDK path isn't set, the default will be used. You can set*
* environment variable ANDROID_NDK or add it in command line as:  *
*  # scons ANDROID_NDK= ...  *
***

*** Info **
*Android Gradle path isn't set, the default will be used. You can set *
* environment variable ANDROID_GRADLE or add it in command line as:   *
*  # scons ANDROID_GRADLE= ...*
***

Copied IoTivity version of config.h to 
/home/jhha85/workspace/iotivity/extlibs/mbedtls/mbedtls/include/mbedtls/config.h
Checking for POSIX Thread Support...yes
HEAD is now at acf202a Fix stack corruption due to calling convention mismatch

scons: *** Two environments with different actions were specified for the same 
target: libcjson_cJSON.o
File "/home/jhha85/workspace/iotivity/extlibs/cjson/SConscript", line 31, in 


Anyone who can resolve the problem?



Thank you.



Best Regards,



Jihun Ha (???/???, Ph.D.)

IoT, IoTivity, OIC | IoT Lab

Software R Center | Samsung Electronics Co., Ltd

Mobile +82 10 2533 7947

jihun.ha at samsung.com | jhha85 at gmail.com





- Original Message -

Sender : ??? mailto:jihun.ha at samsung.com>> Senior 
Engineer/IoT Lab(S/W??)/

Date : 2017-04-11 16:14 (GMT+9)

Title : [dev] Android build fails in 1.3-rel branch



Hi. All.



I'm trying to build iotivity for Android platform but encountering a failure as 
below:

jhha85:~/workspace/iotivity$ scons TARGET_OS=android 
TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 WITH_CLOUD=1
scons: Reading SConscript files ...
AttributeError: 'SConsEnvironment' object has no attribute 'Download':
  File "/home/jhha85/workspace/iotivity/SConstruct", line 28:
SConscript('build_common/SConscript')
  File "/usr/lib/scons/SCons/Script/SConscript.py", line 614:
return method(*args, **kw)
  File "/usr/lib/scons/SCons/Script/SConscript.py", line 551:
return _SConscript(self.fs, *files, **subst_kw)
  File