Giters

DLTcollab / dcurl

Hardware-accelerated Multi-threaded IOTA PoW, drop-in replacement for ccurl

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Remote interface: Build CI

ajblane opened this issue · comments

commented

To test remote interface in CI, we plan to separate tests of remote interface into two case, without RabbitMQ broker and with RabbitMQ broker, via make BUILD_REMOTE=1 BUILD_DEBUG=1 check.

Case I: Without RabbitMQ broker

TODO:

  • Hook functions in remote-common.c

Expected output:

  • Test remote interface and remote workers without RabbitMQ

Case II: With RabbitMQ broker

TODO:

  • Use docker to run RabbitMQ and RabbitMQ Management on node1
  • Use buildkite to early test in a situation of RabbitMQ and two AVX-accelerated remote-workers via make BUILD_REMOTE=1 BUILD_DEBUG=1 check
  • Setup remote workers on FPGA boards
  • Use dd to backup image in SD card
  • Successful test with public RabbitMQ connection with an FPGA board as remote worker via make BUILD_REMOTE=1 BUILD_DEBUG=1 check
  • Successful test with local connection between node1 and FPGA boards via make BUILD_REMOTE=1 BUILD_DEBUG=1 check

Expected output:

  • Automatically test remote interface with RabbitMQ broker
  • Ensure remote workers live via RabbitMQ management