Hello,
building latest textmate after a long time, I am hitting this error:
$ ninja TextMate [9/36] Run test ‘/Users/dusek/build/TextMate/Frameworks/network/test_network’… FAILED: /Users/dusek/build/TextMate/Frameworks/network/test_network && touch /Users/dusek/build/TextMate/Frameworks/network/test_network.run test_network: 1 of 1 test failed: /Users/dusek/Documents/Projects/Contribute/textmate/Frameworks/network/tests/t_download.cc:58: Expected (network::download(network::request_t(url, &myFilter, NULL), &error) == 200), found (0 != 200) [9/36] Run test ‘/Users/dusek/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate’… FAILED: /Users/dusek/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate && touch /Users/dusek/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate.run test_SoftwareUpdate: 5 of 6 tests failed: /Users/dusek/Documents/Projects/Contribute/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:64: Expected (err == "Extracting archive."), found ("Failed to connect to localhost port 64762: Connection refused" != "Extracting archive.") /Users/dusek/Documents/Projects/Contribute/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:73: Expected (err == "Extracting archive."), found ("Failed to connect to localhost port 64762: Connection refused" != "Extracting archive.") /Users/dusek/Documents/Projects/Contribute/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:82: Expected (err == "Bad signature."), found ("Failed to connect to localhost port 64762: Connection refused" != "Bad signature.") /Users/dusek/Documents/Projects/Contribute/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:91: Expected (err == "Bad signature."), found ("Failed to connect to localhost port 64762: Connection refused" != "Bad signature.") /Users/dusek/Documents/Projects/Contribute/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:109: Expected (err == NULL_STR), found ("Failed to connect to localhost port 64762: Connection refused" != "") ninja: build stopped: subcommand failed.
I tried ninja network/coerce and ninja SoftwareUpdate/coerce and they do skip the relevant tests, but these choices do not persist and after running ninja TextMate again, I hit the same failures.
System: Xcode 6.0.1 (i.e. 10.9 SDK) running on Yosemite DP8 (14A361c), happens even on a totally clean rebuild (git clean -xffd; git reset --hard HEAD; rm -rf ~/build/TextMate/; ./configure && ninja)
Is there please anything I can do to make TextMate compile?
Thanks, Boris
On 30 Sep 2014, at 0:49, Boris Dušek wrote:
building latest textmate after a long time, I am hitting this error: […]
Both failures seems to be about not getting through to the test http server TM sets up.
Could it be that you have a proxy setup or something else network related that could explain this?
I tried ninja network/coerce and ninja SoftwareUpdate/coerce and they do skip the relevant tests, but these choices do not persist and after running ninja TextMate again, I hit the same failures.
Unfortunately this no longer work: ninja now references $builddir/.ninja_log to see when something was last succesfully built, so only way to fool it is to edit this file. I need to update the README…
Is there please anything I can do to make TextMate compile?
You can delete the two test files (that fail).
Both failures seems to be about not getting through to the test http server TM sets up.
Could it be that you have a proxy setup or something else network related that could explain this?
I am not aware about having any non-standard setup, I don’t think I ever did anything else network-wise than connecting to a Wi-Fi network.
I tried again this morning (to try if it could be some temporary issue with my internet provider), I also tried connecting to internet through my iPhone as a hot-spot, I still get the same errors in both tests.
I have firewall off in System Preferences > Security & Privacy. In System Preferences > Network > Wi-Fi > Advanced… > Proxies > Select a protocol to configure:, I have no protocol checked.
I tried ninja network/coerce and ninja SoftwareUpdate/coerce and they do skip the relevant tests, but these choices do not persist and after running ninja TextMate again, I hit the same failures.
Unfortunately this no longer work: ninja now references $builddir/.ninja_log to see when something was last succesfully built, so only way to fool it is to edit this file. I need to update the README…
Looking forward to the updated README, as I cannot make sense of how to edit .ninja_log to achieve what I want.
Is there please anything I can do to make TextMate compile?
You can delete the two test files (that fail).
This does not help as on subsequent ninja call, the files get reinstantiated and the same tests fail again.
Thanks for the suggestions so far.
On 30 Sep 2014, at 9:31, Boris Dušek wrote:
Both failures seems to be about not getting through to the test http server TM sets up.
Could it be that you have a proxy setup or something else network related that could explain this?
I am not aware about having any non-standard setup, I don’t think I ever did anything else network-wise than connecting to a Wi-Fi network.
I tried again this morning (to try if it could be some temporary issue with my internet provider), I also tried connecting to internet through my iPhone as a hot-spot, I still get the same errors in both tests.
I mentioned the proxy because TextMate reads the proxy settings but looking at the code, it does skip that for localhost.
And this is code connecting to localhost so internet environment shouldn’t matter.
Re-reading the error you get, it does say: Failed to connect to localhost port 64762: Connection refused.
So the issue seems to be that the server that the test code sets up fails to listen on this port.
The server setup does abort() if it fails to create the listening socket, but it doesn’t report any errors if accept() fails, so I added a message for that and pushed. Though this is grasping at straws…
Have you rebooted since you got this error? Again, grasping at straws, but I have never seen this code fail before and it’s about setting up a listening socket…
[…] Looking forward to the updated README, as I cannot make sense of how to edit .ninja_log to achieve what I want.
Afraid my edit will just remove all info about this. There isn’t any practical solution to skipping tests and I will likely have to make it a ./configure argument.
You can delete the two test files (that fail).
This does not help as on subsequent ninja call, the files get reinstantiated and the same tests fail again.
I think you misunderstand. You need to delete Frameworks/network/tests/t_download.cc — there is no way ninja would restore that.
The server setup does abort() if it fails to create the listening socket, but it doesn’t report any errors if accept() fails, so I added a message for that and pushed. Though this is grasping at straws…
Have you rebooted since you got this error? Again, grasping at straws, but I have never seen this code fail before and it’s about setting up a listening socket…
Running at latest master (639f1d282f381ea227098566cdea96c98fd3f653) and after reboot, a complete clean rebuild. I still get the errors as before, and I get no new error messages that you added in 7cb2330aaef49e3a83ed8147cf2a3e74e91a8e1d.
You can delete the two test files (that fail).
This does not help as on subsequent ninja call, the files get reinstantiated and the same tests fail again.
I think you misunderstand. You need to delete Frameworks/network/tests/t_download.cc — there is no way ninja would restore that.
You are right, I tried removing the test_network and test_network.run files before. Removing the relevant .cc files enabled me to finally compile and launch TextMate :-)
I just ran across the same issue, in my case GlimmerBlocker appeared to interfere. Temporarily disabling GlimmerBlocker allowed the build to continue.
Gerd
On Sep 30, 2014, at 3:28 PM, Boris Dušek me@dusek.me wrote:
The server setup does abort() if it fails to create the listening socket, but it doesn’t report any errors if accept() fails, so I added a message for that and pushed. Though this is grasping at straws…
Have you rebooted since you got this error? Again, grasping at straws, but I have never seen this code fail before and it’s about setting up a listening socket…
Running at latest master (639f1d282f381ea227098566cdea96c98fd3f653) and after reboot, a complete clean rebuild. I still get the errors as before, and I get no new error messages that you added in 7cb2330aaef49e3a83ed8147cf2a3e74e91a8e1d.
You can delete the two test files (that fail).
This does not help as on subsequent ninja call, the files get reinstantiated and the same tests fail again.
I think you misunderstand. You need to delete Frameworks/network/tests/t_download.cc — there is no way ninja would restore that.
You are right, I tried removing the test_network and test_network.run files before. Removing the relevant .cc files enabled me to finally compile and launch TextMate :-)
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Sorry, that wasn't it, just happen to run into a different error I guess. I ended up having to delete both tests too. Still not building, but that is yet a different error.
Gerd
On Oct 26, 2014, at 11:06 AM, Gerd Knops gerti-textmate@bitart.com wrote:
I just ran across the same issue, in my case GlimmerBlocker appeared to interfere. Temporarily disabling GlimmerBlocker allowed the build to continue.
Gerd
On Sep 30, 2014, at 3:28 PM, Boris Dušek me@dusek.me wrote:
The server setup does abort() if it fails to create the listening socket, but it doesn’t report any errors if accept() fails, so I added a message for that and pushed. Though this is grasping at straws…
Have you rebooted since you got this error? Again, grasping at straws, but I have never seen this code fail before and it’s about setting up a listening socket…
Running at latest master (639f1d282f381ea227098566cdea96c98fd3f653) and after reboot, a complete clean rebuild. I still get the errors as before, and I get no new error messages that you added in 7cb2330aaef49e3a83ed8147cf2a3e74e91a8e1d.
You can delete the two test files (that fail).
This does not help as on subsequent ninja call, the files get reinstantiated and the same tests fail again.
I think you misunderstand. You need to delete Frameworks/network/tests/t_download.cc — there is no way ninja would restore that.
You are right, I tried removing the test_network and test_network.run files before. Removing the relevant .cc files enabled me to finally compile and launch TextMate :-)
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-
Allan Odgaard -
Boris Dušek -
Gerd Knops