When developing crash-reporter, or even simply running a dev or test image, there's a few settings to be aware of that control/override runtime behavior.
If testing via ssh, or you otherwise skipped setting up consent, you can opt-in to crash collection by running:
# metrics_client -C
By default, coredumps will be removed after creating minidumps. You can touch /root/.leave_core to change that behavior.
Similarly, if you want Chrome coredumps to be retained, you can touch /mnt/stateful_partition/etc/collect_chrome_crashes.
Crash uploading is disabled on test images. You can force them to be uploaded by running:
# crash_sender -e FORCE_OFFICIAL=1 -e SECONDS_SEND_SPREAD=0
The SECONDS_SEND_SPREAD=0 option is to make crash_sender upload right away. Otherwise it'll sleep a random amount of time (up to 10 minutes) between reports.
If you‘re running a test image, FORCE_OFFICIAL=1 isn’t sufficient. You will also have to touch /run/crash_reporter/crash-test-in-progress. This will bypass all normal OS image checks though, so use this with caution.