Closed tallamjr closed 4 years ago
I edited the sector file (commit https://github.com/alan-turing-institute/bluebird/commit/6ef9c7421264c0baa2c0070650fd3ebbd92cd57c), duplicating the first sector that effectively gets ignored because the corresponding bluebird crashes.
This is hopefully a workable workaround that's going to work for the away day.
I've added this workaround in the scenario generation package.
Just a comment for my own reference :
Regardless of the port it is mapped to, the first instance always seem to die
Closing this - We can investigate if we plan to run that demo again.
It appears that running
run-containers.sh
found in the nats repo (https://github.com/alan-turing-institute/nats/blob/turing-away-day/away-day/run-containers.sh) would previously be able to be set toNUM_BLUEBIRD=3
and this would indeed launch 3 instances of bluebird with a mapping of the following:However after testing today, this was no longer possible and would result in one instance always being 'killed'. To investigate which commit may have caused this issue,
git bisect
was used with the following script:The output of which for a "good" commit is shown below (note the
NUM_BLUEBIRD
andNUM_BLUEBIRD_INSTANCES
are equal)Below is example output from a "bad" commit:
Note they are no longer equal. This was discovered to be introduced in commit
f6c9cd6
This may potentially be linked to issue #76