The wake-on-wifi feature doesn't work with arbitrary packets, it needs special packets.  I can dig out that info if you want, but do we care about testing that path?

Hi Luigi,
This is different from expecting a wake on an incoming packet. I am suspending the system, after starting a ping process and the expectation is that on resume, the ping should go through and no packets should be dropped. 
No pings dropping is the expected behavior as per Sameer, though I haven't understood the reasoning well enough to explain it here. 

With Lucid Sleep since connection to the AP is maintained while the system is in suspended state, I would expect at most one ping to be dropped -- if the echo went out just before the system suspended and the echo response comes back while the system is suspended.

On the other hand, without Lucid Sleep, since the connection to AP would be lost if the suspend duration was more than a few seconds, upon resuming a new scan + association would be needed.  Since this takes 3-4 seconds, any pings during this period would be unsuccessful.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot