Christian wrote:
> On Mi, 27 Nov 2019, Bram Moolenaar wrote: > > > Patch 8.1.2352 > > Problem: CI doesn't cover FreeBSD. > > Solution: Configure Cirrus-CI. (Christian Brabandt, closes #5273) > > Files: .cirrus.yml, README.md > > You are too fast ;) I'll pull the handbrake. > This PR should originally go to my fork so I could test it correctly. I > did not notice that github forwarded the original PR to the upstream > repository, and then I merged by mistake. Yeah, that got mixed up with another change I was trying to push. The github support for rolling back a commit resulted in three changes... Oh, well, should have the right version now, only the commit history looks a bit strange. > > *** ../vim-8.1.2351/.cirrus.yml 2019-11-27 21:54:53.006023177 +0100 > > --- .cirrus.yml 2019-11-27 21:53:11.266504548 +0100 > > *************** > > *** 0 **** > > --- 1,9 ---- > > + freebsd_12_task: > > + freebsd_instance: > > + image: freebsd-12-1-release-amd64 > > + install_script: > > + pkg install -y gettext gmake > > + build_script: > > + - gmake > > + test_script: > > + - gmake test > > *** ../vim-8.1.2351/README.md 2019-02-17 23:26:47.206170316 +0100 > > --- README.md 2019-11-27 21:53:11.266504548 +0100 > > *************** > > *** 2,12 **** > > --- 2,14 ---- > > > > [](https://travis-ci.org/vim/vim) > > [](https://ci.appveyor.com/project/chrisbra/vim) > > + [](https://cirrus-ci.com/github/chrisbra/vim) > > Once cirrus CI is enabled for the vim repository using > https://github.com/marketplace/cirrus-ci you can change the badge link from > github/chrisbra/vim to github/vim/vim > > and have a correct badge for this CI repo. Done that. > Note: My current half-way working patch looks like this: > https://github.com/vim/vim/compare/master...chrisbra:master > > Things to note: > - gmake isn't needed, Vim builds fine with make. It's just patch 8.1.2344 > causes some problems. I'll merge the changes from your .cirrus.yml. > - Vim tests hang at or after test_alot_utf8.vim > - I traced this to `:source!` not correctly working (Vim would hang in > command line mode, waiting for an enter for the `:s` command to complete). > - (I initially tried to add a timer with 15 seconds to runtest.vim, that > calls interrupt() so that > every hanging test would eventually quit, but that just made other tests > hang, so I commented it out) > - Instead, I reset REDIR_TO_NULL, to be able to see where Vim hangs, then it > at least finished, but with > the following failures: > https://api.cirrus-ci.com/v1/task/6555324219129856/logs/test.log > Failures: Well have to find out how to fix them. Let me at least update the link and yml file to the latest, even though it doesn't work yet. > Now its too late, need some sleep. Will have a look later this week. OK, let me know when something works. Although the build on your repo appears to be green now. -- There are three kinds of persons: Those who can count and those who can't. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201911281953.xASJrUrb024557%40masaka.moolenaar.net.
