Skip to content
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

Fix CI for example 8 #95

Merged
merged 16 commits into from
Nov 17, 2020

Conversation

jaimergp
Copy link
Member

@jaimergp jaimergp commented Nov 16, 2020

CI is working, but the code behind #94 is not!

@jaimergp
Copy link
Member Author

I don't know what's wrong. The listeners do not seem to intercept the streams at all :/

@goanpeca
Copy link
Member

goanpeca commented Nov 16, 2020

@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

npm run format
npm run check
npm run build

There should be a JS file also generated from your changes.

?

@jaimergp
Copy link
Member Author

🤦 I thought that was being done on the precommit hook because it took a bit longer than usual. Heh 😬

@goanpeca
Copy link
Member

It works :) !

@@ -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' }}
Copy link
Member

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

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?

@jaimergp
Copy link
Member Author

Ok, finally found the right combo. To check for expected failures:

  • The step that is expected to fail must have continue-on-error: true and an id.
  • The evaluation step needs if: always() and it should check for outcome == 'failure' not conclusion == 'failure'.

This is ready now!

@goanpeca goanpeca added this to the v2.1.0 milestone Nov 17, 2020
@goanpeca goanpeca marked this pull request as ready for review November 17, 2020 00:37
@goanpeca
Copy link
Member

Ok, finally found the right combo. To check for expected failures:

Awesome work @jaimergp. Thanks a lot!

@goanpeca goanpeca merged commit cbc8431 into conda-incubator:master Nov 17, 2020
jaimergp added a commit to jaimergp/setup-miniconda that referenced this pull request Nov 17, 2020
goanpeca added a commit that referenced this pull request Nov 18, 2020
@goanpeca goanpeca removed this from the v2.1.0 milestone Nov 29, 2020
@goanpeca goanpeca added this to the v2.0.1 milestone Nov 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants