haskellPackages: update stackage and hackage#302932
Merged
sternenseemann merged 16 commits intomasterfrom Apr 16, 2024
Merged
Conversation
This commit has been generated by maintainers/scripts/haskell/update-stackage.sh
This commit has been generated by maintainers/scripts/haskell/update-hackage.sh
This commit has been generated by maintainers/scripts/haskell/regenerate-hackage-packages.sh
github-actions
bot
added
the
6.topic: haskell
ofborg
bot
added
8.has: clean-up
By trying to migitate the conflict between two files on a case insensitive fs, we will inevitably end up with a different hash than on case sensitive filesystems. To work around this, we just delete the directory that contains the offending files — luckily it is not important to the build of GHC.
This commit has been generated by maintainers/scripts/haskell/mark-broken.sh based on *evaluation [1805695](https://hydra.nixos.org/eval/1805695) of nixpkgs commit [dc36386](https://github.com/NixOS/nixpkgs/commits/dc363866cb4e84431584cc23be94affe278c36a6) as of 2024-04-16 12:27 UTC* from the haskell-updates jobset on hydra under https://hydra.nixos.org/jobset/nixpkgs/haskell-updates
Member
|
Apparently, some of these changes are now blocking |
Member
|
@vcunat Seems like this is a flaky test failure as I can't reproduce it anymore. I've restarted the offending jobs (at least in Sorry we did not catch this – we've stopped monitoring darwin closely a while ago as we lack the maintainers for that platform. I'll figure something out that at least the channel blocking jobs get more eyes. Edit: Was flaky indeed: https://hydra.nixos.org/build/255668196#tabs-summary. |
Member
|
Oh, OK, just flaky. Certainly not a significant problem, though ideally we'd skip flaky test if it's not difficult. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This Merge
This PR is the regular merge of the
haskell-updatesbranch intomaster.This branch is being continually built and tested by hydra at https://hydra.nixos.org/jobset/nixpkgs/haskell-updates. You may be able to find an up-to-date Hydra build report at cdepillabout/nix-haskell-updates-status.
We roughly aim to merge these
haskell-updatesPRs at least once every two weeks. See the @NixOS/haskell team calendar for who is currently in charge of this branch.haskellPackages Workflow Summary
Our workflow is currently described in
pkgs/development/haskell-modules/HACKING.md.The short version is this:
haskell-updates(normally at the beginning of a merge window).haskell-updatesintomasterevery two weeks.mergeablejob is succeeding on hydra.maintainedpackage is still broken at the time of merge, we will only merge if the maintainer has been pinged 7 days in advance. (If you care about a Haskell package, become a maintainer!)More information about Haskell packages in nixpkgs can be found in the nixpkgs manual.
This is the follow-up to #300455. Come to #haskell:nixos.org if you have any questions.