Fix upstream job URL

enabled an automatic merge when the pipeline for c4a5b619 succeeds

The build-master job fails because of:

[ 1 of 16] Compiling GhcUtil          ( src/GhcUtil.hs, dist/build/GhcUtil.o, dist/build/GhcUtil.dyn_o )
src/GhcUtil.hs:107:19: error:
    Data constructor not in scope: NoBackend :: Backend
    Suggested fix: Perhaps use variable ‘noBackend’ (imported from GHC)
    |
107 |       backend   = NoBackend
    |                   ^^^^^^^^^

I think this is due to ghc@4aa3c5bd, which makes the Backend type abstract. I think this could be fixed by replacing NoBackend with noBackend.

aborted the automatic merge because source branch was updated

added 1 commit

• 673e9fd1 - Patch doctest-0.20.0 to accommodate Backend becoming abstract

Compare with previous version

enabled an automatic merge when the pipeline for 673e9fd1 succeeds

Hm, did the upstream URL for the ghc-9.4 branch actually change? I'm seeing these failures in the build-9.4 jobs:

$ nix build \ # collapsed multi-line command
builder for '/nix/store/jd6a09cw7dssldzh3nd2jkl8w7gywrzz-bindist-version.drv' failed with exit code 1; last 6 log lines:
  unpacking sources
  unpacking source archive /nix/store/0030d9nfajil7lbb5pky2jmpsp1n620z-ghc.tar.xz
  xz: (stdin): File format not recognized
  tar: This does not look like a tar archive
  tar: Exiting with failure status due to previous errors
  do not know how to unpack source archive /nix/store/0030d9nfajil7lbb5pky2jmpsp1n620z-ghc.tar.xz
error: build of '/nix/store/jd6a09cw7dssldzh3nd2jkl8w7gywrzz-bindist-version.drv' failed
(use '--show-trace' to show detailed location information)

@RyanGlScott Yes.. there just aren't any jobs yet for that branch (with that change)

Yes.. there just aren't any jobs yet for that branch (with that change)

Hm, strange. I'm able to download a bindist from the ghc-9.4 branch at commit ghc@89a59a70, which is the latest commit. And yet, the https://gitlab.haskell.org/api/v4/projects/1/jobs/artifacts/ghc-9.4/raw/ghc-x86_64-linux-fedora33-release.tar.xz?job=x86_64-linux-fedora33-release link still 404s for some reason.

I'm guessing the reason this happens is because GitLab is confused because the most recent pipeline here failed. I've restarted that pipeline in an attempt to get things unstuck.

Hm. All of the pipelines here have now passed, but restarting the build-9.4 job still results in the same failure. I'm stumped. Any ideas?

I think the issue is the pipeline which gitlab thinks is for the 9.4 branch is a release pipeline. I think it will be fixed when the next commit is backported to the 9.4 branch.

In the meantime.. I will merge this because it fixes the URL for master so doesn't make things more broken.

merged

mentioned in merge request !250 (merged)

mentioned in issue #61 (closed)