Currently only Linux and Mac (Windows is theoretically possible with //./PIPE/xxx named pipes but less of a priority).
This switches the netlog event processing to use the actual netlog files from Chrome, streamed through a named pipe in realtime instead of relying on the netlog trace events (which break from time to time). This also reduces the number of trace events that need to be pumped and processed at the end of a test pretty significantly.
The actual event processing in netlog.py was cloned from the trace processing with some fixups for the slightly different event structure.
Currently only Linux and Mac (Windows is theoretically possible with //./PIPE/xxx named pipes but less of a priority).
This switches the netlog event processing to use the actual netlog files from Chrome, streamed through a named pipe in realtime instead of relying on the netlog trace events (which break from time to time). This also reduces the number of trace events that need to be pumped and processed at the end of a test pretty significantly.
The actual event processing in netlog.py was cloned from the trace processing with some fixups for the slightly different event structure.
See #526