-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No coverage report generated when used with @embroider/compat@^2.1.0 #374
Comments
Same problem here. Nothing is generated when @embroider/compat is at version ~2.1.0. When downgrading, the coverage folder is only generated when using Repro repository: https://github.com/TRIPTYK/ember-boilerplate .
|
Just ran into this issue as well after upgrading embroider to Note that, for me, after reverting embroider everything is generated properly regardless of the command:
|
This problem was on my side. There was a misconfiguration of a service worker. It now works when downgrading to ~2.0.2. |
Same here. I guess the changelog might help to understand where the issue came from: Does anything ring a bell to anyone? |
After some digging in Embroider and Ember-cli-code-coverage, I found the problem. (thanks @tniezurawski for the idea to look at the diff between the 2 releases). The culprit is this line : https://github.com/embroider-build/embroider/blob/34fec6c15b65ed79a31b9ad9066b5b0004cd4876/packages/compat/src/default-pipeline.ts#L20 Internally, ember-cli-code-coverage uses stableWorkspaceDir from @embroider/compat 0.x for getting the CWD generated by embroider. This method uses a md5 hash to get a semi-random project directory. But the method has changed in @embroider/compat 2.1.0 with a new environment parameter added to the hash. This mismatch in the function implementation will result in a wrong directory guess from ember-cli-code-coverage. Maybe making @embroider/compat an optionalPeerDependency will solve the problem. The idea is to always have the same resolution mechanism than the installed embroider version. I will make a PR shortly. |
@AmauryD That makes sense! I had a feeling that hashing can play a role here. btw I wanted to try your chance to confirm it works for me, but I am getting an error:
Do you know if I pointed to the fork in the wrong way or if that's something else? 🤔 (it's installing without problems)
|
I'm using |
Does #379 fix this? Does anyone know? or is it not just because of a mismatch of embroider versions? |
@AmauryD That works for me 👍 The report is generated. @mansona #379 doesn't fix it for me. Actually, I'm getting an error that I don't observe on version
I'm not sure what is the direct reason 🤷♂️ |
@tniezurawski I just noticed that my PR is out of date now so it wouldn't have the effect of making sure to use the right embroider version since 3.0 was released 🙈 |
~4.8.0
2.0.0-beta-5
,2.1.0
and up^2.1.1
^2.1.1
I've noticed that with starting from @embroider/compat@2.1.0, the code coverage report no longer gets generated. The test build still success, but nothing is outputted in the log and no
/coverage
folder is generated.Once I downgrade
@embroider/compat@2.0.2
, everything seems to work again.The text was updated successfully, but these errors were encountered: