Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Disable unleash-check #9705

Merged
1 commit merged into from
Sep 7, 2021
Merged

Disable unleash-check #9705

1 commit merged into from
Sep 7, 2021

Conversation

joao-paulo-parity
Copy link
Contributor

This line for cargo unleash check ${CARGO_UNLEASH_PKG_DEF} is failing consistently. The last time the status passed on master was on 2021-08-02 and it had been intermittently failing even before that. I suggested to @TriplEight that the check should be disabled until it's taken care of.

cc @gnunicorn

[skip ci]

the last successful run of this check was on f00ec46 and it had been failing even before that

should be re-enabled lated
@bkchr
Copy link
Member

bkchr commented Sep 6, 2021

This will work again after merging this pr: #8615

Which should happen in the near future.

@bkchr
Copy link
Member

bkchr commented Sep 6, 2021

So, not sure we need this.

@joao-paulo-parity
Copy link
Contributor Author

The point of statuses is that developers should care about them and take action when they are failing. If the solution is a "work-in-progress" then disabling the check temporarily is the proper workaround, instead allowing it to fail, since it will always fail, thus providing no value whatsoever. It literally is just noise right now. I think not disabling it in #9474 was a mistake.

I remember when the simnet status was failing often and it was requested for it to be disabled. What is to say about a status which always fails? Not only it does not make sense to have it enabled, but it also might annoy people who see Substrate as perma-red on master for more than a month.

So, not sure we need this.

Fair enough. This is not breaking anything so I'm not interested in pushing it forward if there's any resistance whatsoever. Feel free to re-open and follow up on this if there's interest.

@bkchr
Copy link
Member

bkchr commented Sep 7, 2021

@joao-paulo-parity I get your point and I'm with you that we should have disabled this from the beginning :D

If you like, we can merge it and you push a commit to the pr mentioned above to enable it there again? If you like this idea, reopen and I approve this pr :)

@joao-paulo-parity
Copy link
Contributor Author

I did not push a commit on #8615 (felt out-of-place for me, I don't know...) but left a comment there to re-enable the check once it's ready.

@bkchr bkchr added A2-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders. labels Sep 7, 2021
@joao-paulo-parity
Copy link
Contributor Author

bot merge

@ghost
Copy link

ghost commented Sep 7, 2021

Trying merge.

@ghost ghost merged commit e45dab3 into master Sep 7, 2021
@ghost ghost deleted the jp-disable-unleash branch September 7, 2021 20:57
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A2-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants