You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
As mentioned in #5626 (comment), it would make sense to change our Travis setup so that only the fetch tests are carried out for a given PR containing only ruleset changes, the main benefit being a dramatic decrease in Travis test durations.
One could probably come up with different viable approaches to this, but one that should would be to simply imitate the logic from the existing Travis fetch test, in which the difference from upstream/master is recorded.
Activity
fuglede commentedon Jul 28, 2016
One could probably come up with different viable approaches to this, but one that should would be to simply imitate the logic from the existing Travis fetch test, in which the difference from
upstream/masteris recorded.J0WI commentedon Jul 28, 2016
check_rules.pyshould also be runned for syntax (and code style) testing.fuglede commentedon Jul 31, 2016
Yep, good point!
For PRs that only change rulesets, perform only fetch and rule format…
For PRs that only change rulesets, perform only fetch and rule format…
For PRs that only change rulesets, perform only fetch and rule format…
For PRs that only change rulesets, perform only fetch and rule format…
For PRs that only change rulesets, perform only fetch and rule format…
For PRs that only change rulesets, perform only fetch and rule format…
Merge pull request #6052 from Hainish/ruleset-change-tests