Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

02-tests/task 01 Release 2016.07 - RC1 #22

Closed
BytesGalore opened this issue Jul 26, 2016 · 16 comments
Closed

02-tests/task 01 Release 2016.07 - RC1 #22

BytesGalore opened this issue Jul 26, 2016 · 16 comments

Comments

@BytesGalore
Copy link
Member

BytesGalore commented Jul 26, 2016 •
edited
Loading

Task # 01

Execute all tests on native and check their output:

  • bitarithm_timings
  • bloom_bytes
  • coap
  • conn_ip
  • cpp11_condition_variable
  • cpp11_mutex
  • cpp11_thread
  • driver_adt7310
  • driver_at30tse75x
  • driver_at86rf2xx
  • driver_bh1750
  • driver_bmp180
  • driver_dht -> compiles without warning runs and obviously fails
  • driver_enc28j60
  • driver_encx24j600
  • driver_hdc1000
  • driver_hih6130
  • driver_ina220
  • driver_isl29020
  • driver_isl29125
  • driver_kw2xrf
  • driver_l3g4200d
  • driver_lis3dh
  • driver_lis3mdl
  • driver_lps331ap
  • driver_lsm303dlhc
  • driver_mag3110
  • driver_mma8652
  • driver_mpl3115a2
  • driver_mpu9150
  • driver_mq3
  • driver_nrf24l01p_lowlevel
  • driver_nrfmin
  • driver_nvram_spi
  • driver_pcd8544
  • driver_pir -> compiles without warning runs and obviously fails on GPIO access
  • driver_servo
  • driver_si70xx
  • driver_srf02
  • driver_srf08
  • driver_tcs37727
  • driver_tmp006
  • driver_xbee
  • emb6 -> automatically sets samr21-xpro when BOARD is not set, build with BOARD=native make for the expected build fail
  • fault_handler
  • float -> only shows/spams - on the screen
  • fmt_print
  • gnrc_ipv6_ext
  • gnrc_sixlowpan
  • irq
  • leds
  • libfixmath
  • lwip -> automatically sets iotlab-m3 when BOARD is not set, build with BOARD=native make
  • malloc -> only malloc tested yet since I don't want to wait for filling my whole RAM with 1024 byte chunks
  • minimal
  • msg_send_receive
  • msg_try_receive
  • mutex_order
  • mutex_unlock_and_sleep
  • netdev2_test
  • netstats_l2
  • nhdp
  • periph_adc
  • periph_cpuid
  • periph_dac
  • periph_gpio -> compiles without warning and runs
  • periph_hwrng
  • periph_i2c
  • periph_pwm
  • periph_rtc -> compiles without warning and runs: f: rtc_set_alarm: not implemented
  • periph_rtt
  • periph_spi
  • periph_timer
  • periph_uart -> compiles without warning and runs: UART used for STDIO (the shell): UART_DEV(-1)
  • pipe
  • pkg_cmsis-dsp
  • pkg_jsmn
  • pkg_micro-ecc
  • pkg_u8g2
  • posix_semaphore
  • posix_sleep
  • pthread
  • pthread_barrier
  • pthread_cleanup
  • pthread_condition_variable
  • pthread_cooperation
  • pthread_rwlock
  • pthread_tls
  • saul -> compiles without warning and runs: No SAUL devices present
  • sched_testing
  • shell
  • sizeof_tcb
  • slip (compiled and started, function not tested yet)
  • struct_tm_utility
  • thread_basic
  • thread_cooperation
  • thread_exit
  • thread_flags
  • thread_flood
  • thread_msg
  • thread_msg_avail
  • thread_msg_block_wo_queue
  • thread_msg_block_w_queue
  • thread_msg_seq
  • warn_conflict
  • xtimer_drift
  • xtimer_hang
  • xtimer_longterm
  • xtimer_msg
  • xtimer_msg_receive_timeout
  • xtimer_now64_continuity
  • xtimer_remove
  • xtimer_reset
  • xtimer_usleep_until
  • zep (compiled and started, function not tested yet)

list made manually performing:

ls -1a | sed  -e 's/^/- [ ] /'

in RIOT/tests
@BytesGalore BytesGalore mentioned this issue Jul 26, 2016
Closed
39 tasks
@BytesGalore BytesGalore changed the title Perform test applications on various platforms and check that they run as expected 02-tests Release 2016.07 - RC1 Jul 26, 2016
@BytesGalore
Copy link
Member Author

feel free to edit the list :)

@kYc0o
Copy link
Contributor

kYc0o commented Jul 26, 2016

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

@miri64
Copy link
Member

miri64 commented Jul 26, 2016

@BytesGalore @kYc0o can not reproduce, sadly :(

@BytesGalore
Copy link
Member Author

@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

@miri64
Copy link
Member

miri64 commented Jul 26, 2016

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

@miri64
Copy link
Member

miri64 commented Jul 26, 2016 •
edited
Loading

(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)

@miri64
Copy link
Member

miri64 commented Jul 26, 2016

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

@BytesGalore
Copy link
Member Author

@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

@kYc0o
Copy link
Contributor

kYc0o commented Jul 26, 2016

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

@BytesGalore
Copy link
Member Author

@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

@kYc0o
Copy link
Contributor

kYc0o commented Jul 26, 2016

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

@BytesGalore BytesGalore changed the title 02-tests Release 2016.07 - RC1 02-tests/task 01 Release 2016.07 - RC1 Jul 27, 2016
@miri64
Copy link
Member

miri64 commented Jul 27, 2016

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

@BytesGalore
Copy link
Member Author

@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.

@BytesGalore
Copy link
Member Author

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)

@miri64
Copy link
Member

miri64 commented Jul 27, 2016

👍

@BytesGalore
Copy link
Member Author

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

@miri64 miri64 closed this as completed Oct 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@miri64 @BytesGalore @kYc0o