haskell-ci problems

older
About adding msync and anonymous...

Sven Panne

13 Nov 2021 13 Nov '21

7:02 a.m.

I am (finally) about to switch my Haskell projects on GitHub from Travis CI to GitHub Actions, so I've tried haskell-ci (from HEAD) for creating the workflow files from the .cabal files. But something went wrong, see https://github.com/haskell-opengl/StateVar/actions/runs/1456427818/workflow Initially, I thought that this failure was related to using the latest and greatest GHC version, so I removed that, but the failure stays: https://github.com/haskell-opengl/StateVar/actions/runs/1456437461/workflow Any hints on what I'm doing wrong? Or is it a haskell-ci bug? Cheers, S.

Attachments:

attachment.html (text/html — 857 bytes)

Show replies by date

Mikolaj Konarski

13 Nov 13 Nov

7:27 a.m.

Hi Sven, Not sure about this particular error, but haskell-ci does not yet seem fully updated to the travis/GHA switch and Ubuntu repo/gchup switch. In particular, there is no Ubuntu package for GHC 9.2.1 that you are requesting and there may never be. I'd advise to use ghcup instead. There are at least some examples about that in haskell-ci repo (IIRC, at least the haskell-ci CI job itself), even if the script is not up to the task. Contributions welcome. Cheers, Mikolaj On Sat, Nov 13, 2021 at 1:04 PM Sven Panne wrote:

...

I am (finally) about to switch my Haskell projects on GitHub from Travis CI to GitHub Actions, so I've tried haskell-ci (from HEAD) for creating the workflow files from the .cabal files. But something went wrong, see https://github.com/haskell-opengl/StateVar/actions/runs/1456427818/workflow Initially, I thought that this failure was related to using the latest and greatest GHC version, so I removed that, but the failure stays: https://github.com/haskell-opengl/StateVar/actions/runs/1456437461/workflow

Any hints on what I'm doing wrong? Or is it a haskell-ci bug?

Cheers, S. _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Sven Panne

8:02 a.m.

Am Sa., 13. Nov. 2021 um 13:27 Uhr schrieb Mikolaj Konarski < mikolaj@well-typed.com>:

...

Not sure about this particular error, but haskell-ci does not yet seem fully updated to the travis/GHA switch and Ubuntu repo/gchup switch.

My point is: I don't care about how the workflow gets the tools and compilers, I was just hoping to have a simple way to generate a workflow from a .cabal file. :-( Currently I am too busy with other things that I can't dive into the details of GitHub Actions, haskell-ci, etc., I can just offer testing haskell-ci patches etc. The project I used as a trial balloon for haskell-ci is really dead simple, how are other projects handling this? It must be an extremely common use case, and I doubt that everybody writes the workflows by hand: This would be silly, basically all needed information is already in the .cabal file. Other projects like e.g. lens seem to use haskell-ci successfully, see https://github.com/ekmett/lens/blob/master/.github/workflows/haskell-ci.yml. But that YAML file looks quite a bit different from what haskell-ci has generated for my project. Why?

...

In particular, there is no Ubuntu package for GHC 9.2.1 that you are requesting and there may never be.

That's totally OK, the workflow seems to reference hvr's PPA. And as I said: Even when I remove 9.2.1, I get the exact same error again for 9.0.1.

...

I'd advise to use ghcup instead. There are at least some examples about that in haskell-ci repo (IIRC, at least the haskell-ci CI job itself), even if the script is not up to the task. Contributions welcome.

Personally I use stack exclusively, totally ignoring cabal and ghcup. But that should be fine as long as the workflow is doing whatever it needs to do with those tools. As usual, the Haskell tool ecosystem is giving me a hard time... :´-( Cheers, S.

Mikolaj Konarski

8:39 a.m.

...

I can just offer testing haskell-ci patches etc.

Thank you. I'm sure other haskell-ci contributors can use this help, if they read this. In general, that's a great idea, supporting our developers in other ways than just code contributions, e.g., via general positivity, appreciation, goodwill, expressions of hope, uplifting user stories. They are bombarded with (impersonal) negativity all the time via bug reports.

...

The project I used as a trial balloon for haskell-ci is really dead simple, how are other projects handling this? It must be an extremely common use case, and I doubt that everybody writes the workflows by hand: This would be silly, basically all needed information is already in the .cabal file.

I'm afraid, since hvr stopped updating the PPA images (and other things), the Haskell tool ecosystem is in the very sorry and silly state you describe. Given that at this stage it's too late to help hvr, let's make sure to support Julian with ghcup (and other things) so that our ecosystem doesn't break up again, once we port haskell-ci to ghcup (if I'm guessing correctly where haskell-ci is going).

...

Other projects like e.g. lens seem to use haskell-ci successfully, see https://github.com/ekmett/lens/blob/master/.github/workflows/haskell-ci.yml. But that YAML file looks quite a bit different from what haskell-ci has generated for my project. Why?

Because it's been edited by hand for 11 months.

...

As usual, the Haskell tool ecosystem is giving me a hard time... :´-(

I sympathise. All the best, Mikolaj

Mikolaj Konarski

10:05 a.m.

BTW, Sven, my sources say, running `haskell-ci 'github'` as opposed to `haskell-ci 'travis'` may give better results. On Sat, Nov 13, 2021 at 2:39 PM Mikolaj Konarski wrote:

...

...
I can just offer testing haskell-ci patches etc.

Thank you. I'm sure other haskell-ci contributors can use this help, if they read this. In general, that's a great idea, supporting our developers in other ways than just code contributions, e.g., via general positivity, appreciation, goodwill, expressions of hope, uplifting user stories. They are bombarded with (impersonal) negativity all the time via bug reports.

...
The project I used as a trial balloon for haskell-ci is really dead simple, how are other projects handling this? It must be an extremely common use case, and I doubt that everybody writes the workflows by hand: This would be silly, basically all needed information is already in the .cabal file.

I'm afraid, since hvr stopped updating the PPA images (and other things), the Haskell tool ecosystem is in the very sorry and silly state you describe. Given that at this stage it's too late to help hvr, let's make sure to support Julian with ghcup (and other things) so that our ecosystem doesn't break up again, once we port haskell-ci to ghcup (if I'm guessing correctly where haskell-ci is going).

...
Other projects like e.g. lens seem to use haskell-ci successfully, see https://github.com/ekmett/lens/blob/master/.github/workflows/haskell-ci.yml. But that YAML file looks quite a bit different from what haskell-ci has generated for my project. Why?

Because it's been edited by hand for 11 months.

...
As usual, the Haskell tool ecosystem is giving me a hard time... :´-(

I sympathise.

All the best, Mikolaj

Mikolaj Konarski

10:47 a.m.

Off-topic, would it be possible to reduce the latency of mail.haskell.org? It's quite frustrating if your message is a dupe and even more if it seems as if the other person ignored your message and wrote the stuff one again. While, in fact, the messages were 10 minutes in flight and then arrived in reverse order. On Sat, Nov 13, 2021 at 4:05 PM Mikolaj Konarski wrote:

...

BTW, Sven, my sources say, running `haskell-ci 'github'` as opposed to `haskell-ci 'travis'` may give better results.

On Sat, Nov 13, 2021 at 2:39 PM Mikolaj Konarski wrote:

...
...
I can just offer testing haskell-ci patches etc.

Thank you. I'm sure other haskell-ci contributors can use this help, if they read this. In general, that's a great idea, supporting our developers in other ways than just code contributions, e.g., via general positivity, appreciation, goodwill, expressions of hope, uplifting user stories. They are bombarded with (impersonal) negativity all the time via bug reports.

...
The project I used as a trial balloon for haskell-ci is really dead simple, how are other projects handling this? It must be an extremely common use case, and I doubt that everybody writes the workflows by hand: This would be silly, basically all needed information is already in the .cabal file.

I'm afraid, since hvr stopped updating the PPA images (and other things), the Haskell tool ecosystem is in the very sorry and silly state you describe. Given that at this stage it's too late to help hvr, let's make sure to support Julian with ghcup (and other things) so that our ecosystem doesn't break up again, once we port haskell-ci to ghcup (if I'm guessing correctly where haskell-ci is going).

...
Other projects like e.g. lens seem to use haskell-ci successfully, see https://github.com/ekmett/lens/blob/master/.github/workflows/haskell-ci.yml. But that YAML file looks quite a bit different from what haskell-ci has generated for my project. Why?

Because it's been edited by hand for 11 months.

...
As usual, the Haskell tool ecosystem is giving me a hard time... :´-(

I sympathise.

All the best, Mikolaj

Simon Jakobi

10:55 a.m.

Huh, I think there must be something amiss between mail.haskell.org and GMail. I have not received your message from 4:05 PM at all, nor the message from Tom Ellis that I see at https://mail.haskell.org/pipermail/haskell-cafe/2021-November/134848.html. Am Sa., 13. Nov. 2021 um 16:48 Uhr schrieb Mikolaj Konarski :

...

Off-topic, would it be possible to reduce the latency of mail.haskell.org?

It's quite frustrating if your message is a dupe and even more if it seems as if the other person ignored your message and wrote the stuff one again. While, in fact, the messages were 10 minutes in flight and then arrived in reverse order.

On Sat, Nov 13, 2021 at 4:05 PM Mikolaj Konarski wrote:

...
BTW, Sven, my sources say, running `haskell-ci 'github'` as opposed to `haskell-ci 'travis'` may give better results.

On Sat, Nov 13, 2021 at 2:39 PM Mikolaj Konarski wrote:

...
...
I can just offer testing haskell-ci patches etc.

Thank you. I'm sure other haskell-ci contributors can use this help, if they read this. In general, that's a great idea, supporting our developers in other ways than just code contributions, e.g., via general positivity, appreciation, goodwill, expressions of hope, uplifting user stories. They are bombarded with (impersonal) negativity all the time via bug reports.

...
The project I used as a trial balloon for haskell-ci is really dead simple, how are other projects handling this? It must be an extremely common use case, and I doubt that everybody writes the workflows by hand: This would be silly, basically all needed information is already in the .cabal file.

I'm afraid, since hvr stopped updating the PPA images (and other things), the Haskell tool ecosystem is in the very sorry and silly state you describe. Given that at this stage it's too late to help hvr, let's make sure to support Julian with ghcup (and other things) so that our ecosystem doesn't break up again, once we port haskell-ci to ghcup (if I'm guessing correctly where haskell-ci is going).

...
Other projects like e.g. lens seem to use haskell-ci successfully, see https://github.com/ekmett/lens/blob/master/.github/workflows/haskell-ci.yml. But that YAML file looks quite a bit different from what haskell-ci has generated for my project. Why?

Because it's been edited by hand for 11 months.

...
As usual, the Haskell tool ecosystem is giving me a hard time... :´-(

I sympathise.

All the best, Mikolaj

_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Mikolaj Konarski

16 Nov 16 Nov

5:02 a.m.

...

I have not received your message from 4:05 PM at all, nor the message from Tom Ellis that I see at

Apparently avoiding both spam and lost emails is impossible nowadays, but I'm told the situation should improve after a recent upgrade, update of a SPF record for one of mail.haskell.org servers and gradually while our servers are regaining reputation. For all of us on the list: let's not assume somebody that is repeating our point has seen our email --- it may have been lost or withheld for a time. Makes sense to ask for confirmation and also try to join divergent threads of the same email discussion (if the topic did not diverge). On Sat, Nov 13, 2021 at 4:56 PM Simon Jakobi wrote:

...

Huh, I think there must be something amiss between mail.haskell.org and GMail.

I have not received your message from 4:05 PM at all, nor the message from Tom Ellis that I see at https://mail.haskell.org/pipermail/haskell-cafe/2021-November/134848.html.

Am Sa., 13. Nov. 2021 um 16:48 Uhr schrieb Mikolaj Konarski :

...
Off-topic, would it be possible to reduce the latency of mail.haskell.org?

It's quite frustrating if your message is a dupe and even more if it seems as if the other person ignored your message and wrote the stuff one again. While, in fact, the messages were 10 minutes in flight and then arrived in reverse order.

On Sat, Nov 13, 2021 at 4:05 PM Mikolaj Konarski wrote:

...
BTW, Sven, my sources say, running `haskell-ci 'github'` as opposed to `haskell-ci 'travis'` may give better results.

On Sat, Nov 13, 2021 at 2:39 PM Mikolaj Konarski wrote:

...
...
I can just offer testing haskell-ci patches etc.

Thank you. I'm sure other haskell-ci contributors can use this help, if they read this. In general, that's a great idea, supporting our developers in other ways than just code contributions, e.g., via general positivity, appreciation, goodwill, expressions of hope, uplifting user stories. They are bombarded with (impersonal) negativity all the time via bug reports.

...
The project I used as a trial balloon for haskell-ci is really dead simple, how are other projects handling this? It must be an extremely common use case, and I doubt that everybody writes the workflows by hand: This would be silly, basically all needed information is already in the .cabal file.

I'm afraid, since hvr stopped updating the PPA images (and other things), the Haskell tool ecosystem is in the very sorry and silly state you describe. Given that at this stage it's too late to help hvr, let's make sure to support Julian with ghcup (and other things) so that our ecosystem doesn't break up again, once we port haskell-ci to ghcup (if I'm guessing correctly where haskell-ci is going).

...
Other projects like e.g. lens seem to use haskell-ci successfully, see https://github.com/ekmett/lens/blob/master/.github/workflows/haskell-ci.yml. But that YAML file looks quite a bit different from what haskell-ci has generated for my project. Why?

Because it's been edited by hand for 11 months.

...
As usual, the Haskell tool ecosystem is giving me a hard time... :´-(

I sympathise.

All the best, Mikolaj

_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Simon Jakobi

13 Nov 13 Nov

10:11 a.m.

Hi Sven, the issue is in fact very simple. You have generated a config for Travis CI, not one for GitHub Actions! This is indicated by the command `haskell-ci travis` here: https://github.com/haskell-opengl/StateVar/actions/runs/1456427818/workflow#... In order to generate a GHA config, you should use the command `haskell-ci github`. If you need any further help, I recommend that you use the haskell-ci issue tracker: https://github.com/haskell-CI/haskell-ci/issues Oleg and Ryan have so far been very responsive and helpful when I needed assistance. Happy CIing, Simon Am Sa., 13. Nov. 2021 um 13:03 Uhr schrieb Sven Panne :

...

I am (finally) about to switch my Haskell projects on GitHub from Travis CI to GitHub Actions, so I've tried haskell-ci (from HEAD) for creating the workflow files from the .cabal files. But something went wrong, see https://github.com/haskell-opengl/StateVar/actions/runs/1456427818/workflow Initially, I thought that this failure was related to using the latest and greatest GHC version, so I removed that, but the failure stays: https://github.com/haskell-opengl/StateVar/actions/runs/1456437461/workflow

Any hints on what I'm doing wrong? Or is it a haskell-ci bug?

Cheers, S. _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Tom Ellis

10:17 a.m.

I can confirm that this indeed works: https://github.com/tomjaguarpaw/StateVar/blob/96f55e23eedd6f7e8665eb388deb60... https://github.com/tomjaguarpaw/StateVar/runs/4199126514 Tom On Sat, Nov 13, 2021 at 04:11:13PM +0100, Simon Jakobi via Haskell-Cafe wrote:

...

the issue is in fact very simple. You have generated a config for Travis CI, not one for GitHub Actions!

Am Sa., 13. Nov. 2021 um 13:03 Uhr schrieb Sven Panne :

...
I am (finally) about to switch my Haskell projects on GitHub from Travis CI to GitHub Actions, so I've tried haskell-ci (from HEAD) for creating the workflow files from the .cabal files. But something went wrong, see https://github.com/haskell-opengl/StateVar/actions/runs/1456427818/workflow Initially, I thought that this failure was related to using the latest and greatest GHC version, so I removed that, but the failure stays: https://github.com/haskell-opengl/StateVar/actions/runs/1456437461/workflow

Any hints on what I'm doing wrong? Or is it a haskell-ci bug?

Sven Panne

11:34 a.m.

Am Sa., 13. Nov. 2021 um 16:11 Uhr schrieb Simon Jakobi < simon.jakobi@googlemail.com>:

...

the issue is in fact very simple. You have generated a config for Travis CI, not one for GitHub Actions! [...]

Embarrassing... :-} Thanks for the quick help, things are looking much better now, even GHC 9.2.1 works out-of-the-box! I *did* look into the haskell-ci code to figure out how to generate a workflow instead of a Travis CI configuration, but my copy-n-paste-fu was obviously not strong enough. :-] The haskell-ci README could need some love: GitHub actions are not mentioned at all (you have to use "git log" to figure out that they are supported), OTOH Travis CI is all over the place, although it is effectively dead. Thanks to the haskell-ci team, the tool is great for lazy people like me! Just a tiny bit of documentation plus some more advertising would be great... Cheers, S.

1281

Age (days ago)

1284

Last active (days ago)

List overview

Download

10 comments

4 participants

participants (4)

Mikolaj Konarski
Simon Jakobi
Sven Panne
Tom Ellis