extconf.rb returns exit code 0 on failure about appsignal-ruby HOT 5 CLOSED

This by design. Rule nummer one is never break the customer's app/deploy. So the gem still installs, logs the issue and doesn't prevent a deploy from completing.

from appsignal-ruby.

Ah so that applies here as well.. Quite annoying to debug, a silent failed install, but I still have to figure out all the moving parts I guess. It could maybe benefit from a message to STDOUT if something goes wrong

from appsignal-ruby.

There should have been a clear message in appsignal.log. If that wasn't the case I'd consider that a bug. 👍 on warning to stdout during bundle if that's possible.

from appsignal-ruby.

The message was in ext/install.log and ext/mkmf.log, but incomplete clean up of the test files made it look like everything had gone ok until I noticed the agent was running older code.

from appsignal-ruby.

I think we can close this one now. I've added mkmf.log to appsignal diagnose, so we can now see this information.

from appsignal-ruby.