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.
For what it's worth (which is not all that much), this is not a huge issue for the day-to-day Travis usage: the test only compares with the current master branch. This means that the fetch test is run for PRs but not for the merge commit, allowing us to ignore the results if needed, and after confirming that the false negatives are indeed false. (See e.g. this build for an example.)
However, this issue of course impacts the periodic database-wide runs of the checker which will still give false negatives.
Activity
fuglede commentedon May 16, 2016
For what it's worth (which is not all that much), this is not a huge issue for the day-to-day Travis usage: the test only compares with the current master branch. This means that the fetch test is run for PRs but not for the merge commit, allowing us to ignore the results if needed, and after confirming that the false negatives are indeed false. (See e.g. this build for an example.)
However, this issue of course impacts the periodic database-wide runs of the checker which will still give false negatives.
fuglede commentedon May 25, 2016
@J0WI: Will you keep an eye on whether or not this was sufficient to kill off the issues?
J0WI commentedon May 25, 2016
Sure. I'll reopen if I still run in this issue.