Bro working well on Mac OS High Sierra, just a couple test failures

Development
1

I had no problems after the upgrade to High Sierra on my “production” box, and I had no troubles compiling Bro 2.5.1 on my laptop.

I did, however, get a two errors in the test suite.

core.truncation ... failed
  % 'btest-diff output' failed unexpectedly (exit code 1)
  % cat .diag
  == File ===============================
  #separator \x09
  #set_separator ,
  #empty_field (empty)
  #unset_field -
  #path weird
  #open 2017-10-04-18-48-40
  #fields ts uid id.orig_h id.orig_p id.resp_h id.resp_p name addl notice peer
  #types time string addr port addr port string string bool string
  1334160095.895421 - - - - - truncated_IP bro
  #close 2017-10-04-18-48-40
  #separator \x09
  #set_separator ,
  #empty_field (empty)
  #unset_field -
  #path weird
  #open 2017-10-04-18-48-41
  #fields ts uid id.orig_h id.orig_p id.resp_h id.resp_p name addl notice peer
  #types time string addr port addr port string string bool string
  1334156241.519125 - - - - - truncated_IP bro
  #close 2017-10-04-18-48-41
  #separator \x09
  #set_separator ,
  #empty_field (empty)
  #unset_field -
  #path weird
  #open 2017-10-04-18-48-41
  #fields ts uid id.orig_h id.orig_p id.resp_h id.resp_p name addl notice peer
  #types time string addr port addr port string string bool string
  1334094648.590126 - - - - - truncated_IP bro
  #close 2017-10-04-18-48-41
  #separator \x09
  #set_separator ,
  #empty_field (empty)
  #unset_field -
  #path weird
  #open 2017-10-04-18-48-43
  #fields ts uid id.orig_h id.orig_p id.resp_h id.resp_p name addl notice peer
  #types time string addr port addr port string string bool string
  1338328954.078361 - - - - - internally_truncated_header - F bro
  #close 2017-10-04-18-48-43
  #separator \x09
  #set_separator ,
  #empty_field (empty)
  #unset_field -
  #path weird
  #open 2017-10-04-18-48-43
  #fields ts uid id.orig_h id.orig_p id.resp_h id.resp_p name addl notice peer
  #types time string addr port addr port string string bool string
  1404148886.981015 - - - - - bad_IP_checksumbro
  1404148887.011158 CHhAvVGS1DHFjwGM9 192.168.4.149 51293 72.21.91.29 443 bad_TCP_checksum - F bro
  #close 2017-10-04-18-48-43
  == Diff ===============================
  --- /tmp/test-diff.62112.output.baseline.tmp 2017-10-04 18:48:43.000000000 +0000
  +++ /tmp/test-diff.62112.output.tmp 2017-10-04 18:48:43.000000000 +0000
  @@ -46,5 +46,6 @@
   #open XXXX-XX-XX-XX-XX-XX
   #fields ts uid id.orig_h id.orig_p id.resp_h id.resp_p name addl notice peer
   #types time string addr port addr port string string bool string
  -0.000000 - - - - - truncated_link_header bro
  +XXXXXXXXXX.XXXXXX - - - - - bad_IP_checksumbro
  +XXXXXXXXXX.XXXXXX CHhAvVGS1DHFjwGM9 192.168.4.149 51293 72.21.91.29 443 bad_TCP_checksum - F bro
   #close XXXX-XX-XX-XX-XX-XX

2

The first test failure was fixed after the release of 2.5.1. The second
failure looks like another race condition (try again a few times and it
will likely pass).

3

Right you are. 4th time’s a charm. :slight_smile: