-
Notifications
You must be signed in to change notification settings - Fork 52
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
Ease debugging, fix some CI issues, tweak folder structure #200
Ease debugging, fix some CI issues, tweak folder structure #200
Conversation
The fact that one mirror fails in the above test and others follow working is test enough for me A single failing mirror should fail, but it's confusing to have an error annotation for a success (via continue-on-error) while not being able to suppress it via GitHub Actions
Might simply be that the bug is already fixed and we need to bump rebar3
We're getting Access Denied for Fetching registry from "https://repo.hex.pm:443/registry.ets.gz?"
if: ${{ steps.failing-setup-beam.outcome == 'success' }} | ||
run: | | ||
echo "Action is expected to fail" | ||
exit 1 |
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.
Why remove this?
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.
We get an annotation with an error, which lead us to think that there was an issue, but then there wasn't because the action is β . It's basically very misleading. We can add a non-workflow action test (e.g. JavaScript) to test the same condition, though, if it's absolutely necessary.
Released in |
Opening as draft to try and troubleshoot #199. (and then some π)This:
debugLog
functionconsole.
with appropriate calls tocore.
console.
__tests__
totest
test-projects
totest/projects
matchers
rebar_core
breaking are fixednpm run tests
are fixedCI is all β again. We still get errors regarding hitting the GitHub API all too often, but that's outside the scope of this PR and there's already an ongoing PR for this.