-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix CI for example 8 #95
Fix CI for example 8 #95
Conversation
I don't know what's wrong. The listeners do not seem to intercept the streams at all :/ |
@jaimergp I think you need to do the build step so that the assets get compiled and then that is what is used by actions. Are you running
There should be a JS file also generated from your changes. ? |
🤦 I thought that was being done on the precommit hook because it took a bit longer than usual. Heh 😬 |
It works :) ! |
.github/workflows/example-8.yml
Outdated
@@ -27,7 +27,7 @@ jobs: | |||
environment-file: etc/example-faulty-environment.yml | |||
- name: Check previous step failed | |||
shell: bash | |||
run: ${{ steps.setup-miniconda.conclusion == "failure" }} | |||
run: ${{ steps.setup-miniconda.conclusion == 'failure' }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So since the previous step fails, this will never be reached.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, I fixed that and it runs now but the CI result is still red. I thought last successful one counted but maybe we have to setup that explicitly?
Ok, finally found the right combo. To check for expected failures:
This is ready now! |
Awesome work @jaimergp. Thanks a lot! |
CI is working, but the code behind #94 is not!