Bump fatsd to master (issue #16)

commit 7d9f90ebe9dd3a7f6af1fbb97d8cc228fb0fded4
Author: David Bauer <mail@david-bauer.net>
Date:   Thu Jul 25 18:51:25 2019 +0200

    resolve: fix segmentation fault with musl >1.1.20

    When compiled with musl >1.1.20, fastd will crash in case it can't
    resolve a peers hostname. This is due to a changed implementation of
    freeaddrinfo in musl 1.1.21 onwards.

    This segfault is fixed by not calling freeaddrinfo in case the supplied
    pointer is null.

    Signed-off-by: David Bauer <mail@david-bauer.net>
7 jobs for fastd-bump in 0 seconds (queued for 115 minutes and 53 seconds)
Status Name Job ID Coverage
  Build
failed ar71xx.generic #1489
m2runner

failed ar71xx.tiny #1488
m2runner

failed ath79.nand #1494
m2runner

failed ipq40xx.generic #1492
m2runner

failed lantiq.xrx200 #1493
m2runner

failed ramips.mt7621 #1491
m2runner

failed x86.generic #1490
m2runner

 
Name Stage Failure
failed
ar71xx.tiny Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
ar71xx.generic Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
x86.generic Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
ramips.mt7621 Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
ipq40xx.generic Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
lantiq.xrx200 Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
ath79.nand Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log