Spam detection software, running on the system "mail.haskell.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: I'm back at my computer and am investigating. I don't see the problem I feared, but I do see some anomalies. I'll update once it's back to normal. On Sat, 18 Mar 2023 at 17:55, Bryan Richter <bryan@haskell.foundation> wrote: [...] Content analysis details: (5.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record 5.0 UNWANTED_LANGUAGE_BODY BODY: Message written in an undesired language 0.0 HTML_MESSAGE BODY: HTML included in message 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5000] 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.
I did find that some jobs were being retried repeatedly. I have deployed a workaround to prevent this from continuing. The problem was related to T18623 behaving strangely, and I've opened https://gitlab.haskell.org/ghc/ghc/-/issues/23139 so GHC devs can have a look at it. On Sun, 19 Mar 2023 at 13:27, Bryan Richter <bryan@haskell.foundation> wrote:
I'm back at my computer and am investigating. I don't see the problem I feared, but I do see some anomalies. I'll update once it's back to normal.
On Sat, 18 Mar 2023 at 17:55, Bryan Richter <bryan@haskell.foundation> wrote:
I'm away from my computer for the day, but yes there were some jobs that got stuck in a restart loop. See https://gitlab.haskell.org/ghc/ghc/-/issues/23094#note_487426 . Unfortunately I don't know if there are others, but I did fix the root cause of that particular loop.
On Sat, 18 Mar 2023, 15.06 Sam Derbyshire, <sam.derbyshire@gmail.com> wrote:
I think there's a problem with jobs restarting, on my renamer MR <https://gitlab.haskell.org/ghc/ghc/-/merge_requests/8686> there were 5 full pipelines running at once. I had to cancel some of them, but also it seems some got cancelled by some new CI pipelines restarting.
On Sat, 18 Mar 2023 at 13:59, Simon Peyton Jones < simon.peytonjones@gmail.com> wrote:
All GHC CI pipelines seem stalled, sadly
e.g. https://gitlab.haskell.org/ghc/ghc/-/merge_requests/10123/pipelines
Can someone unglue it?
Thanks!
Simon _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Hoo boy... now I've fixed an even *bigger* problem that is pretty embarrassing. https://gitlab.haskell.org/ghc/ghc-perf-import/-/commit/67238099e9c3478ba591... It's time to give this service a proper testsuite. On Sun, 19 Mar 2023 at 14:42, Bryan Richter <bryan@haskell.foundation> wrote:
I did find that some jobs were being retried repeatedly. I have deployed a workaround to prevent this from continuing. The problem was related to T18623 behaving strangely, and I've opened https://gitlab.haskell.org/ghc/ghc/-/issues/23139 so GHC devs can have a look at it.
On Sun, 19 Mar 2023 at 13:27, Bryan Richter <bryan@haskell.foundation> wrote:
I'm back at my computer and am investigating. I don't see the problem I feared, but I do see some anomalies. I'll update once it's back to normal.
On Sat, 18 Mar 2023 at 17:55, Bryan Richter <bryan@haskell.foundation> wrote:
I'm away from my computer for the day, but yes there were some jobs that got stuck in a restart loop. See https://gitlab.haskell.org/ghc/ghc/-/issues/23094#note_487426 . Unfortunately I don't know if there are others, but I did fix the root cause of that particular loop.
On Sat, 18 Mar 2023, 15.06 Sam Derbyshire, <sam.derbyshire@gmail.com> wrote:
I think there's a problem with jobs restarting, on my renamer MR <https://gitlab.haskell.org/ghc/ghc/-/merge_requests/8686> there were 5 full pipelines running at once. I had to cancel some of them, but also it seems some got cancelled by some new CI pipelines restarting.
On Sat, 18 Mar 2023 at 13:59, Simon Peyton Jones < simon.peytonjones@gmail.com> wrote:
All GHC CI pipelines seem stalled, sadly
e.g. https://gitlab.haskell.org/ghc/ghc/-/merge_requests/10123/pipelines
Can someone unglue it?
Thanks!
Simon _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
participants (1)
-
Bryan Richter