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.

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

02-tests/task 02 Release 2016.07 - RC1 #23

Closed
BytesGalore opened this issue Jul 27, 2016 · 1 comment
Closed

02-tests/task 02 Release 2016.07 - RC1 #23

BytesGalore opened this issue Jul 27, 2016 · 1 comment

Comments

@BytesGalore
Copy link
Member

BytesGalore commented Jul 27, 2016

Task # 02

Perform a subset of tests on iotlab-m3 node:

  • bitarithm_timings
  • bloom_bytes
  • coap
  • conn_ip sent 3 pings out (ping6)
  • cpp11_condition_variable
  • cpp11_mutex
  • cpp11_thread
  • driver_adt7310
  • driver_at30tse75x
  • driver_at86rf2xx
  • driver_bh1750
  • driver_bmp180
  • driver_dht -> results in expected behaviour: gets stuck at dht_read(dev, &temp, &hum), since no DHT 11/22 temperature and humidity sensor is attached
  • driver_enc28j60
  • driver_encx24j600
  • driver_hdc1000 -> results in expected behaviour: Initializing HDC1000 sensor at I2C_0... [Failed]
  • driver_hih6130
  • driver_ina220
  • driver_isl29020
  • driver_isl29125
  • driver_kw2xrf
  • driver_l3g4200d
  • driver_lis3dh
  • driver_lis3mdl
  • driver_lps331ap
  • driver_lsm303dlhc
  • driver_mag3110
  • driver_mma8652 -> results in expected behaviour: Initializing MMA8652 accelerometer at I2C_0... [Failed]
  • driver_mpl3115a2
  • driver_mpu9150
  • driver_mq3
  • driver_nrf24l01p_lowlevel
  • driver_nrfmin
  • driver_nvram_spi -> results in expected behaviour: Verifying contents... [Failed]
  • driver_pcd8544
  • driver_pir
  • driver_servo
  • driver_si70xx
  • driver_srf02
  • driver_srf08 -> results in expected behaviour: no values are printed, since no SRF08 ultrasonic sensor is attached
  • driver_tcs37727
  • driver_tmp006
  • driver_xbee -> results in expected behaviour: the device cannot be configured, since no xbee shield is attached
  • emb6
  • fault_handler
  • float -> only shows/spams - on the screen
  • fmt_print
  • gnrc_ipv6_ext
  • gnrc_sixlowpan
  • irq
  • leds
  • libfixmath
  • lwip
  • malloc
  • 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
  • periph_hwrng
  • periph_i2c
  • periph_pwm
  • periph_rtc
  • periph_rtt
  • periph_spi
  • periph_timer
  • periph_uart
  • 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
  • sched_testing
  • shell
  • sizeof_tcb
  • slip
  • 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 -> I ran it for a handful minutes: max drift/jitter is about +-35 us (these high values occured ~ 4 times a min)
  • xtimer_hang
  • xtimer_longterm
  • xtimer_msg
  • xtimer_msg_receive_timeout
  • xtimer_now64_continuity
  • xtimer_remove
  • xtimer_reset
  • xtimer_usleep_until
  • zep

list made manually by executing:

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

in RIOT/tests and removing unittests et al. from the list

@BytesGalore
Copy link
Member Author

tests performed on:
RIOT-OS/RIOT@b5cb68b
with:
gcc version 5.3.1 20160307 (release) [ARM/embedded-5-branch revision 234589] (GNU Tools for ARM Embedded Processors)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants