| # 00:39:04 | idwer | quits : Ping timeout: 256 seconds |
| # 10:33:41 | idwer | joins #crosstool-ng |
| # 15:41:30 | feepbot | quits : Ping timeout: 265 seconds |
| # 15:44:18 | feepbot | joins #crosstool-ng |
| # 16:17:21 | feepbot | quits : Ping timeout: 250 seconds |
| # 16:47:24 | feepbot | joins #crosstool-ng |
| # 18:17:08 | feepbot | quits : Ping timeout: 265 seconds |
| # 18:26:55 | feepbot | joins #crosstool-ng |
| # 23:22:40 | bhundven | It's been a rough couple weeks, friends. I hope you're all doing well. |
| # 23:23:43 | veremitz | alas I fear its set to continue for several more .. |
| # 23:24:36 | veremitz | however, hopefully a new temporary norm is starting to kick in |
| # 23:25:50 | bhundven | There is some good news. |
| # 23:25:52 | bhundven | https://gitlab.com/crosstool-ng/crosstool-ng/pipelines/132742730 |
| # 23:25:58 | bhundven | I've gotten more tests to pass on gitlab |
| # 23:26:13 | veremitz | \o/ |
| # 23:27:18 | bhundven | I think if I keep that gitlab-ci branch local on my computer. Delete the gitlab project, and re-create it with syncing issues and PRs, we could probably start cutting over to gitlab. |
| # 23:27:56 | bhundven | the one problem is that if we go down that path, we'll need to maybe setup a runner outside of gitlab, or we'll go over cpu time on gitlab, since our pipeline is so big. |
| # 23:29:25 | bhundven | I'm looking through PRs on github, since I think chris and alexey are busy |