02-tests/task 01 Release 2016.07 - RC1 about release-specs HOT 16 CLOSED

feel free to edit the list :)

from release-specs.

Great! Thanks @BytesGalore @miri64 any hints on emb6 and lwip errors?

from release-specs.

@BytesGalore @kYc0o can not reproduce, sadly :(

from release-specs.

@kYc0o @miri64 emb6 sets the samr21-xpro board as default [1].
using:

BOARD=native make

results in the expected behaviour, i.e. unsatisfied requirements and build fail
[1] https://github.com/RIOT-OS/RIOT/blob/master/tests/emb6/Makefile#L5

from release-specs.

The reason this application sets it as a default is because there is no native support for it.

from release-specs.

(emb6 only has IEEE 802.15.4 support so porting it for native wouldn't make much sense anyway, at least until RIOT-OS/RIOT#5582 is merged)

from release-specs.

((also also: RIOT-OS/RIOT#4672 needs to be solved, so auto-init also works for non GNRC-stacks))

from release-specs.

@miri64 yup I expected it to not compile and run but I expected a specific behaviour, i.e. failing with an unsatisfied requirements warning.

Similar applies for lwip the iotlab-m3 board is set when BOARD is not provided [1].
using:

BOARD=native make

results in a successful build and allows to start the compiled test-application (though untested yet)

[1] https://github.com/RIOT-OS/RIOT/blob/master/tests/lwip/Makefile#L3

from release-specs.

So what's the conclusion on this? Can we say that the test ran successfully?

from release-specs.

@kYc0o don't know, I guess lwip is not supposed to run on native but it successfully builds and the test-application can be started.
Beside this uncertainty I would say the test ran successfully.

btw. Since we have no release branch yet, I performed the tests on:
RIOT-OS/RIOT@b5cb68b

from release-specs.

Ok great. Yes that was the last commit before I started the tests too.

from release-specs.

lwIP is supposed to run on native! So if it runs what is the problem? :/

from release-specs.

@miri64 if its supposed to run on native I propose that we change the default set BOARD accordingly.

So if it runs what is the problem?

When I start it on native ifconfig states:

ifconfig
ET_00:  inet6 fe80::d8c3:d5ff:fe46:7582

but sending some packet fails:

> udp send 2001::1 8080 1
udp send 2001::1 8080 1
could not send
> ip send 2001::1 inet6 10
ip send 2001::1 inet6 10
could not send

probably I just failed to use it properly.

from release-specs.

ok, I failed 😊

> udp send fe80::1 8080 1
udp send fe80::1 8080 1
Success: send 1 byte to [fe80::1]:8080)
> ip send fe80::1 inet6 1
ip send fe80::1 inet6 1
Success: send 1 byte to fe80::1 (next header: 0)

from release-specs.

👍

from release-specs.

I propose RIOT-OS/RIOT#5698 to change the default BOARD to native for lwip

from release-specs.