# Haskell Foundation DevOps Weekly Update, 2022-11-09

**URL:** <https://discourse.haskell.org/t/haskell-foundation-devops-weekly-update-2022-11-09/5285>\
**Category:** Haskell Foundation\
**Created:** [November 9, 2022, 12:52pm UTC](https://discourse.haskell.org/t/haskell-foundation-devops-weekly-update-2022-11-09/5285 "2022-11-09T12:52:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chreekat](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/chreekat/32/2669_2.png) [@chreekat](https://discourse.haskell.org/u/chreekat)\
**Post date:** [November 9, 2022, 12:52pm UTC](https://discourse.haskell.org/t/haskell-foundation-devops-weekly-update-2022-11-09/5285/1 "2022-11-09T12:52:06Z")

</div>

Hello!

This has been an eventful week with lots of operation surprises. But I’m really happy to be completely unblocked on the looming hardware migration, and that is my focus right now!

Done

- Created a replacement Arm runner as part of the [ongoing server migration](https://gitlab.haskell.org/ghc/ghc/-/issues/22289).
- Fixed one [followup issue](https://gitlab.haskell.org/ghc/ghc/-/merge_requests/9279) in the quest to make nightly tests more reliable.
  - _(This showed up on last week’s list, but I had to babysit CI this week to actually get it through.)_

- Researched GitLab service errors.
  - Failure to display pipeline info
    - _Fixed by bgamari with a service upgrade/restart_

  - Disk space outage
    - _Fixed by me with a Nix garbage collection_

  - Increased rate of failures from CI runners
    - _Fixed itself; i.e. the failures were intermittent and should be tracked as such_

- Got access to the last few systems I need in order to finish migrating away from end-of-life hardware!

Doing

- Removing armv7 (32-bit Arm) tests, since they are frequently broken and only supported by end-of-life CI hardware at the moment. I made an issue tracking [renewed support for the architecture](https://gitlab.haskell.org/ghc/ghc/-/issues/22409).
- Continuing preparation for the hardware migration. In particular, today I am planning the DNS changes that will be required.

Coming up

- The actual hardware migration! It took a while to remove all the organizational blockers, but that’s done now, so I can just work and get it done.
- A grand return to the good old days of squashing spurious failures and silencing fragile tests.