-
Notifications
You must be signed in to change notification settings - Fork 3
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
Running ember test fails #2
Comments
Interesting! Can you post your One thing to note: I currently do not support any kind of configuration around where to find the Ember app just yet; we make a hard assumption that the root of Git repo is the Ember application (or addon). I have this step up for https://github.com/alexlafroscia/ember-steps I don't know if you can see this screen, but I have the action/workflow going here |
Thanks for the quick response. I have this in
|
Ah! Looks like you're missing an action to actually install your dependencies. The idea with Actions is to keep them small and focused. To that end, this action intentionally does not perform the initial dependency installation itself; it assumes a previous step provides an environment with the dependencies installed. If you check out the screenshot in the README, you can see that there's a separate initial action that does the dependency install. Assuming you are using workflow "Test and deploy" {
on = "push"
resolves = ["Run ember tests"]
}
action "Install dependencies" {
uses = "nuxt/actions-yarn@node-10"
args = "install"
}
action "Run ember tests" {
uses = "alexlafroscia/actions-ember-testing@master"
needs = ["Install Dependencies"]
} If you are using action "Install dependencies" {
uses = "actions/npm@master"
args = "install"
} I will update the README to make this more clear. |
Just to follow up, I added a more basic configuration example in the You can find a better explanation of how to set things up here! https://github.com/alexlafroscia/actions-ember-testing/wiki |
Thanks, Alex, I modified it as per your instructions and that will probably work (I'll tell if it doesn't). I'm very new to Github Actions but what you say (that they are atomic, like build steps) makes perfect sense, and already loving the idea. |
Great! If I can help any more, please let me know. |
I'd set up the flow as you describe in the wiki but it still doesn't work, giving me another error in the "Install dependencies" step:
It seems like |
Hmm, or maybe it's rather this: |
That's interesting... sorry it's not working for you! Do you have any dependencies with a I haven't run into that error before, either on a local machine or with this action. |
You're spot on, again :) I do have a couple of // package.json
"devDependencies": {
"ember-cli": "github:ember-cli/ember-cli#807f56e2e434f716757de02fd1f2c3251dadaf6f",
"ember-composable-helpers": "DockYard/ember-composable-helpers",
"ember-data": "github:emberjs/data#1df833396855d956b817540923dd89338463fec2",
"ember-source": "https://s3.amazonaws.com/builds.emberjs.com/canary/shas/888d6b1ec8240aacb7e1ccbefd42002d22d40068.tgz",
} (The ember-composable-helpers one has nothing to do with Octane. I think everybody is using the "githhub" version as a release hasn't been cut for quite a while. And now that I'm writing this I see they've now released a new version.) |
I see. Interesting... This action doesn't actually do any of the dependency installation, so I'm not sure how much I can help. I'd suggest making an issue over at the If there's anything else I can help with, please let me know! |
Hey Alex,
Thank you for putting this together. I tried it on one of my projects and got a failing build:
Locally the
ember
executable is there, maybe not in the Docker build?The text was updated successfully, but these errors were encountered: