{"thread":{"id":"56083","subject":"unit tests / cirrus ci fails","startedAt":"2021-07-09T13:31:06Z","lastAt":"2021-07-10T20:43:03Z","messageCount":4,"participants":["Fabian Stelzer","Đoàn Trần Công Danh","Philippe Blain"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"429542","messageId":"a7aca5f5-3a5e-b13c-ccae-3e515c774420@gigacodes.de","threadId":"56083","inReplyTo":null,"subject":"unit tests / cirrus ci fails","fromName":"Fabian Stelzer","fromEmail":"fs@gigacodes.de","sentAt":"2021-07-09T13:31:01Z","receivedAt":"2021-07-09T13:31:06Z","isPatch":false,"sender":{"key":"fs@gigacodes.de","avatar":"https://avatars.githubusercontent.com/u/564858?v=4"},"body":"Hi,\ni'm having a issue with a failing test on my pull request.\nhttps://github.com/git/git/pull/1041/checks?check_run_id=3028222798\n\nI have added a bunch of new tests and they fail on the freebsd12 test \nthat's run via gitgitgadget.\nIs there any way to enable verbose / debug output on these or a simple \nway to run tests manually in the same environment?\n\nI had no issues with the full test suite on fedora / centos linux except \nfor \"t0500-progress-display.sh\"\nwhich seems to be a different issue. this test fails in master as well \non my fedora34 but works just fine on centos8.\n\nKind regards,\nFabian Stelzer\n\n"},{"id":"429550","messageId":"YOhmAGig//yfABWv@danh.dev","threadId":"56083","inReplyTo":"a7aca5f5-3a5e-b13c-ccae-3e515c774420@gigacodes.de","subject":"Re: unit tests / cirrus ci fails","fromName":"Đoàn Trần Công Danh","fromEmail":"congdanhqx@gmail.com","sentAt":"2021-07-09T15:06:56Z","receivedAt":"2021-07-09T15:07:01Z","isPatch":false,"sender":{"key":"congdanhqx@gmail.com","avatar":"https://avatars.githubusercontent.com/u/42673067?v=4"},"body":"On 2021-07-09 15:31:01+0200, Fabian Stelzer <fs@gigacodes.de> wrote:\n> Hi,\n> i'm having a issue with a failing test on my pull request.\n> https://github.com/git/git/pull/1041/checks?check_run_id=3028222798\n> \n> I have added a bunch of new tests and they fail on the freebsd12 test that's\n> run via gitgitgadget.\n> Is there any way to enable verbose / debug output on these or a simple way\n> to run tests manually in the same environment?\n\nI don't know about cirrus CI, but, skimming over the log, it run into\nfatal error after skipping t4202.71, I think the bashism in\n\"test_lazy_prereq GPGSSH\" is the culprit.\n\n\"|&\" in \"ssh_version=$(ssh-keygen -Y find-principals |& grep -q \"unknown option\")\"\n\n> I had no issues with the full test suite on fedora / centos linux except for\n> \"t0500-progress-display.sh\"\n> which seems to be a different issue. this test fails in master as well on my\n> fedora34 but works just fine on centos8.\n> \n> Kind regards,\n> Fabian Stelzer\n> \n\n-- \nDanh\n"},{"id":"429560","messageId":"db030e49-edb0-8f4b-0e51-a89b2a4a47a8@gigacodes.de","threadId":"56083","inReplyTo":"YOhmAGig//yfABWv@danh.dev","subject":"Re: unit tests / cirrus ci fails","fromName":"Fabian Stelzer","fromEmail":"fs@gigacodes.de","sentAt":"2021-07-09T16:04:01Z","receivedAt":"2021-07-09T16:04:09Z","isPatch":false,"sender":{"key":"fs@gigacodes.de","avatar":"https://avatars.githubusercontent.com/u/564858?v=4"},"body":"On 09.07.21 17:06, Đoàn Trần Công Danh wrote:\n\n> On 2021-07-09 15:31:01+0200, Fabian Stelzer <fs@gigacodes.de> wrote:\n>> Hi,\n>> i'm having a issue with a failing test on my pull request.\n>> https://github.com/git/git/pull/1041/checks?check_run_id=3028222798\n>>\n>> I have added a bunch of new tests and they fail on the freebsd12 test that's\n>> run via gitgitgadget.\n>> Is there any way to enable verbose / debug output on these or a simple way\n>> to run tests manually in the same environment?\n> I don't know about cirrus CI, but, skimming over the log, it run into\n> fatal error after skipping t4202.71, I think the bashism in\n> \"test_lazy_prereq GPGSSH\" is the culprit.\n>\n> \"|&\" in \"ssh_version=$(ssh-keygen -Y find-principals |& grep -q \"unknown option\")\"\nThanks, that was indeed (part of) the problem.\nThe new tests themselves are failing now and i have no idea why on \nfreebsd :/\nAre there detailed logs publicly available from the CI runs?\nOr is my only option to set up a freebsd 12 vm to try to replicate this?\nDoes the ci simply run \"make test\" or is there another mechanism involved?\n"},{"id":"429644","messageId":"dba84da7-f6ec-37b3-4322-378af9249d54@gmail.com","threadId":"56083","inReplyTo":"db030e49-edb0-8f4b-0e51-a89b2a4a47a8@gigacodes.de","subject":"Re: unit tests / cirrus ci fails","fromName":"Philippe Blain","fromEmail":"levraiphilippeblain@gmail.com","sentAt":"2021-07-10T20:42:55Z","receivedAt":"2021-07-10T20:43:03Z","isPatch":false,"sender":{"key":"levraiphilippeblain@gmail.com","avatar":"https://avatars.githubusercontent.com/u/44212482?v=4"},"body":"Hi Fabian,\n\nLe 2021-07-09 à 12:04, Fabian Stelzer a écrit :\n\n> The new tests themselves are failing now and i have no idea why on freebsd :/\n> Are there detailed logs publicly available from the CI runs?\n\nthe logs should be accessible on the \"Checks\" tab of your PR\n  if you are logged into GitHub. But I don't think there is more\nto see than what's shown there.\n\n> Or is my only option to set up a freebsd 12 vm to try to replicate this?\n> Does the ci simply run \"make test\" or is there another mechanism involved?\n> \n\nI managed to log into the Cirrus-CI FreeBSD VM using tunshell [1].\nI found out about it at [2]. Here's the commit in my fork [3]\n\n0. Create a Cirrus-CI account and give it access to your fork of Git\n1. Create the tunshell session at [1]\n2. Run the local script on your local host\n3. Copy the remote script in '.cirrus.yml' in you branch\n    (ex. as the first step of the \"test_script:\" section), commit and push to GitHub\n4. wait for the build to start on Cirrus and the tunshell client on your machine\n    should connect you to the VM.\n5. Go to /tmp/cirrus-ci-build in the VM to find the git.git checkout\n\nCaveat: your public IP will be viewable in the Cirrus log.\n\n[1] https://tunshell.com/go\n[3] https://github.com/phil-blain/git/commit/b47d803ee1ba83100702cb80c93e18c74d787dce\n[2] https://github.com/cirruslabs/cirrus-ci-docs/issues/432\n"}]}