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
add percy #159
add percy #159
Conversation
6bcc134
to
55c1c24
Compare
69e4579
to
c9d4540
Compare
bdbd786
to
5122035
Compare
5194999
to
745b860
Compare
Ok, the bug should be fixed! Can you try against master? (Need to some testing with a few customers before we will tag this as an official release)
If you're curious, the bug was that we were only setting up ember-percy's finalizer IFF you had called Let me know if that works! |
Looks great now. Thanks Mike! Longstanding PR now mergeable 😄 |
👍 |
FYI, the fix is now released as ember-percy v1.2.1. |
@fotinakis I rewrote the commit to put the real version number in, and now it seems to be hung again. |
Oof sorry about that, there was a transient networking error (https://travis-ci.org/kellyselden/package-hint-historic-resolver/jobs/161520196). If you click rebuild in travis or push a new commit it should work. |
@fotinakis I restarted the entire Travis build last night and this morning, and percy is still hanging. I haven't tried rewriting the commit yet, because I wanted to give you a chance to debug if there is another hidden issue. |
Damn, it looks like Travis re-uses build numbers when you click "restart" in the UI ... so that makes it very hard for us to tell the difference between builds when we aggregate from parallel builds. So, can you I'll think about some long-term architecture fixes we might be able to do to fix this, parallel builds dependent on CI services are hard. |
All good now, thanks @fotinakis |
No description provided.