Fix documentation of BLE GattCharacteristic

[akosthekiss]

The constructor doc incorrectly suggested that only short (16-bit)
UUIDs were accepted. The same doc also referred to properties
instead of characteristics. (And to "value length", which seemed to
be completely out of place in the context of the current code.)

Status

READY

Migrations

NO

[akosthekiss]

Tried to track down why some CIs turned red but did not get far. (Travis is green, that's for sure.)

Circle CI reports:

Usage: nosetests [options]

nosetests: error: no such option: -v

((nosetests -v "--with-xunit --xunit-file=/tmp/circle-junit.3yam3fc/nosetests/nosetests.xml")) returned exit code 2

This seems to be unrelated to this PR.

To the Jenkins details, I have no access. Any directions are appreciated.

[0xc0170]

@akosthekiss Hello, we are investigating CI failures. circle ci is now disabled, I am checking how this was enabled in first place.

[0xc0170]

cc @pan-

[theotherjimmy]

@akosthekiss Could you change the sha of the last commit to kick out Circle CI? You can do this with git commit --amend with no changes.

[akosthekiss]

@theotherjimmy done

[0xc0170]

/morph test

[mbed-bot]

Result: ABORTED

Your command has finished executing! Here's what you wrote!

/morph test

[adbridge]

retest uvisor

[akosthekiss]

Thought I'd give CIs a chance to run again by rebasing PR to latest master.

[akosthekiss]

What now? I feel a bit lost.

[0xc0170]

@mazimkhan I can't acces uvisor CI link via details here? It was retriggered 3 days ago, can you review?

@akosthekiss I restarted jenkins CI, and we will run one more CI.

[akosthekiss]

@mazimkhan @adbridge Could I ask for some help with Cam-CI uvisor, again?

[0xc0170]

retest uvisor

[0xc0170]

/morph test

[mbed-bot]

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1546

All builds and test passed!

[akosthekiss]

retest uvisor