Redis exits with code 1 or null, node-foreman does not appear to wait as foreman does

[MattWalston]

Procfile:
redis: redis-server /usr/local/etc/redis.conf

7:15:50 PM redis.1 |  41698:C 26 Aug 19:15:50.252 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7:15:50 PM redis.1 |  41698:C 26 Aug 19:15:50.253 # Redis version=4.0.11, bits=64, commit=00000000, modified=0, pid=41698, just started
7:15:50 PM redis.1 |  41698:C 26 Aug 19:15:50.253 # Configuration loaded
7:15:50 PM redis.1 |                  _._                                                  
7:15:50 PM redis.1 |             _.-``__ ''-._                                             
7:15:50 PM redis.1 |        _.-``    `.  `_.  ''-._           Redis 4.0.11 (00000000/0) 64 bit
(...)       
7:15:50 PM redis.1 |  41698:M 26 Aug 19:15:50.255 # Server initialized
7:15:50 PM redis.1 |  41698:M 26 Aug 19:15:50.255 * DB loaded from disk: 0.000 seconds
7:15:50 PM redis.1 |  41698:M 26 Aug 19:15:50.255 * Ready to accept connections
^C[WARN] Interrupted by User
[DONE] Killing all processes with signal  SIGINT
7:16:29 PM redis.1 |  41698:signal-handler (1535325389) Received SIGINT scheduling shutdown...
7:16:29 PM redis.1 |  41698:signal-handler (1535325389) You insist... exiting now.
7:16:29 PM redis.1 Exited with exit code null

Ruby foreman behaves as expected. Sometimes redis will exit code 1 and heroku local will consistently exit code 1. It appears as though the node-foreman does not wait for the redis-server process to terminate.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.