[GitHub Actions] Unknown (empty) errors in build logs

[aiartefact]

I'm running a simple gtest project built with cmake with the following yml-file:

Build is successful but logs are not visible due to some unknown (empty) error:

However, raw logs indicate successful build completion and contain successful output from gtest:

It seems that accessing raw logs every time should "solve" the problem, but at least it is inconvenient. Besides, those empty error messages indicate some kind of a problem.
So, my questions are: What's wrong with conventional logs and how to fix it?

[airtower-luna]

I've seen similar with strict mode in uBlock Origin, where I was blocking requests to other domains by default. I had to allow requests to the server the logs are loaded from (pipelines.actions.githubusercontent.com, which is a CNAME for l-0007.l-msedge.net).

If you have any kind of adblocker or similar, check if it's blocking requests when you try to load the logs.

[aiartefact]

Thank you very much for the idea where to search! I haven't searched in that direction because my AdGuard was disabled for GitHub. But your answer gave me idea to double-check every single extension. The problem was hiding in NoScript extension. Its icon indicated all scripts to be enabled, but ...actions.githubusercontent.com was marked as blocked. As soon as it was enabled logs became visible:

For anyone who will ever face similar problem I suggest to double-check every single extension in the browser and network activity.