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

ci: Fix --index-state for hackage roundtrip tests (backport #10285) #10305

Merged
merged 4 commits into from
Sep 13, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Aug 30, 2024

As a principle, tests which are required for CI to pass should be
reproducible and not depending on external resources changes or being
modified. The hackage tests currently violate this by depending on the
latest index state from hackage. This is problematic because until the
test is fixed all merges into master are blocked. Even though the
patches in question have nothing to do with the test.

It would be more suitable for a nightly job to run on the latest index
and for normal CI to run with a fixed index which is updated
periodically in a controlled manner.

Fixes #10284


This is an automatic backport of pull request #10285 done by Mergify.

@geekosaur geekosaur added the squash+merge me Tell Mergify Bot to squash-merge label Aug 30, 2024
We need to fix the index-state we test against so a new bad cabal file
doesn't take down the CI for everyone.

Towards #10284

(cherry picked from commit 8e4d167)
As a principle, tests which are required for CI to pass should be
reproducible and not depending on external resources changes or being
modified. The hackage tests currently violate this by depending on the
latest index state from hackage. This is problematic because until the
test is fixed all merges into master are blocked. Even though the
patches in question have nothing to do with the test.

It would be more suitable for a nightly job to run on the latest index
and for normal CI to run with a fixed index which is updated
periodically in a controlled manner.

Fixes #10284

(cherry picked from commit 31507b1)
@geekosaur geekosaur force-pushed the mergify/bp/3.12/pr-10285 branch 2 times, most recently from 62658bc to 0e119ce Compare August 31, 2024 01:47
@geekosaur
Copy link
Collaborator

Welp. Guess that PR I cherry-picked doesn't actually fix it.

@geekosaur
Copy link
Collaborator

So random windows jobs are still failing in various ways (ghci ExitFailure, fd N:end of file, occasionally timeouts).

@geekosaur
Copy link
Collaborator

Was there a reason this was canceled?

(cherry picked from commit 4aade2d)
@geekosaur
Copy link
Collaborator

Cherry-picked f90d059 to try to get CI to pass.

@geekosaur geekosaur closed this Sep 3, 2024
@mergify mergify bot deleted the mergify/bp/3.12/pr-10285 branch September 3, 2024 03:06
@geekosaur geekosaur restored the mergify/bp/3.12/pr-10285 branch September 13, 2024 00:14
@geekosaur geekosaur reopened this Sep 13, 2024
@geekosaur
Copy link
Collaborator

@mergify refresh

Copy link
Contributor Author

mergify bot commented Sep 13, 2024

refresh

✅ Pull request refreshed

@mergify mergify bot merged commit 3b13288 into 3.12 Sep 13, 2024
51 checks passed
@mergify mergify bot deleted the mergify/bp/3.12/pr-10285 branch September 13, 2024 05:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport squash+merge me Tell Mergify Bot to squash-merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants