BullseyeCoverageError

[anon20000101]

Hi,

I just found a “BullseyeCoverageError.txt” file in my User/Username directory. The content reads:

BullseyeCoverage 8.14.7 error 15: Cannot find H:\Faire\Unity Technologies\Unity Hub/test.cov. COVFILE is not set, errno=2. Executable is \?\C:\Users\Username\AppData\Local\Temp\01f06849-aa2f-450e-8882-6b3125ca3b8c.tmp.node

It’s dated today 12:04 which must be when I launched the Hub today.

I closed the Hub and restarted it; the file updated itself. New content:

BullseyeCoverage 8.14.7 error 15: Cannot find H:\Faire\Unity Technologies\Unity Hub/test.cov. COVFILE is not set, errno=2. Executable is \?\C:\Users\Username\AppData\Local\Temp\e4f4e902-351d-4e52-8d4b-381e9a49f92a.tmp.node

What is it? What must I do about that?

Edit: I searched for previous versions of the file; it appeared the first time on December 18, after I updated the Hub to version 1.4.0.

[anon20000101]

@Charles_Beauchemin or anyone involved in the Hub development; I know that it’s holiday times but I hope someone is paying attention to that; the file is still there.

I’ve searched my whole computer for a “test.cov” file: it is nowhere to be found.

[Charles_Beauchemin]

Hi APSchmidt,
Our response time is a little bit slower this week as we still have many devs on vacation, but we’ll get back to you shortly.

[anon20000101]

@Charles_Beauchemin

Hi APSchmidt,
Our response time is a little bit slower this week as we still have many devs on vacation, but we’ll get back to you shortly.

Ah thank you. Sorry, I was worrying that my thread had gone unnoticed.

Happy new year!

[ReaktorDave]

That file is created everytime I start Unity Hub. Please fix.

[dri_richard]

According to Process Monitor, Unity Hub attempts to create that file thousand of times per second - see attachment.

[ReaktorDave]

So Unity Technologies is screwing up our SSD drives.

[mathieub]

Hi there,

Thank you for reporting this and sorry for the inconvenience.
We’re investigating that.

[superpig]

It looks like we accidentally built the Hub with our code coverage tooling left enabled. Sorry about that!

We’re fixing our buildfarm to make sure that the coverage tooling is properly turned off by default for everything, and then we can do a new version of the Hub which should no longer attempt to create this file. Either I or someone on the Hub team will update this thread once the fixed version is out.