[squid-dev] Build failed in Jenkins: 3.HEAD-amd64-OpenBSD-5.4 #211
See http://build.squid-cache.org/job/3.HEAD-amd64-OpenBSD-5.4/211/changes Changes: [Amos Jeffries] RFC 6176 compliance ... prohibits use of SSLv2. https://tools.ietf.org/html/rfc6176 Remove the documentation and support for configuring Squid with SSLv2-only. Explicitly enable the SSL_NO_SSLv2 option when provided by the library to prevent implicit fallback. Remove support for ssloptions= values which are for SSLv2-specific bugs. Due to the way they are implemented with atoi() sslversion=N configuration will still accept the values for SSLv2-only. But the context creation will now unconditionally produce SSLv2 not supported errors if the now undocumented values are attempted. [Christos Tsantilas] Make helper queue size configurable patch: default queue size for external_acl fix The default queue size value is never set for external_acl helpers. -- [...truncated 7005 lines...] ../../src/tests/testHttp1Parser.cc:846: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:860: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:861: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:862: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:863: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:864: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:865: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:866: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:867: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:868: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:869: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:870: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:871: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:872: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:873: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:874: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:875: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:884: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:885: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:886: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:887: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:888: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:889: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:890: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:891: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:892: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:893: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:894: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:895: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:896: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:897: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:898: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:899: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:958: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:959: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:960: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:961: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:962: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:963: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:964: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:965: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:966: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:967: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:968: error: expected
Re: [squid-dev] FYI: the C++11 roadmap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I will try to respond here and not separately. The main issue is like a recursive function that runs and has a specific end. - From my expirence For CentOS(6.5): We start and run the same thing again the next time. So the first exit case I would suggest is to let 3.5 be less compatible with C++11 due to the complexity of CentOS admins. If there will be a change in CentOS even throw EPEL to the GCC compiler we can then rethink out path again. Also there are couple other repos for CentOS but they convert the OS to something outside of CentOS BASE support scope. For Ubuntu(14.01): Their version is: gcc-4.8 Their LTS version shows stability but has some bugs here and there. I have built a deb file for ubuntu and can rebuild it again but I will need to practice before I would say I have mastered it enough to build it for each release. So my opinion is to give stability more weight and to make sure that 3.4.9 and forward will prove that we care about it. Once we can compare Ubuntu and CentOS and say that we want to support CentOS by building RPMs, we can then verify with the CentOS community about the options for newer version of GCC and make it even possible for them to upgrade the packages on a near EOL OS. I think that admins should be able to do their update\upgrade job and if they have a really big system they have some minions that can help them with the process and in most cases would like the challenge!! * where do we have a list of C++11 based items list? Eliezer On 05/05/2014 05:21 PM, Amos Jeffries wrote: I have just announced the change in 3.4.5 regarding C++11 support and accompanied it with a notice that GCC verion 4.8 is likely to become the minimum version later this calendar year. As it stands (discussed earlier): * Squid-3.4 needs to build with any GCC 4.0+ version with C++03. * Squid-3.6 will need to build with C++11. * The Squid-3.5 situation is still in limbo and will depend on how long we go before it branches. We have a growing list of items needing C++11 features for simpler implementation. At this point I am going to throw a peg out and say Sept or Oct for starting to use C++11 specific code features. That should still allow us enough time to complete and branch 3.5. But if feature completion takes too long, so be it. Cheers Amos -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUYHaAAAoJENxnfXtQ8ZQUOMoIAIxZ0TIlE8ULIO1kbiWnK/aH HWTX3vD0e5qowdbR9XsJsfKHDE+BDdoOyc9oEI7U+bwROUfYswL/eOkrWGv3U7pW n6+BzkcKNcJVIGSDYD2EbHLgIHphG30QcNyjW4WW+vxftFFCSrypjVQG4yIsNmVi NVi/bXG2LVI4++H73HT06I5W/oHx4Sr8j6usPoCdn+qdHlrXM9QNtI8DEI63DZJQ u2+NEemv5/eBA4ymHXW5Ye03i4y998gaNHrM4POgoaDGIqea8LpyFek4u4/WF+ky hGTUzBkCizBmc35b59DH6R/FtYDZjgQFVIsxoo+Sn+TEH2rDcSoBH71YVnRlUrM= =cGcl -END PGP SIGNATURE- ___ squid-dev mailing list squid-dev@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-dev
[squid-dev] Build failed in Jenkins: 3.HEAD-amd64-centos-7-clang #87
See http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/87/changes Changes: [Amos Jeffries] C++11: cleanup compiler flag detection logics Annotate what GCC version is required to pass the -std=c++11 and -std=c++0x feature detection tests. Disable the tests for features we do not use that require GCC 4.5+. This should allow Squid to continue building on older OS and compilers at least until we start using those features. -- [...truncated 8651 lines...] depbase=`echo tests/stub_http.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_http.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_http.o ../../src/tests/stub_http.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_icp.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_icp.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_icp.o ../../src/tests/stub_icp.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_internal.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_internal.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_internal.o ../../src/tests/stub_internal.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_ipc.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_ipc.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_ipc.o ../../src/tests/stub_ipc.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_ipcache.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_ipcache.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_ipcache.o ../../src/tests/stub_ipcache.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_libeui.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\;
[squid-dev] Jenkins build is back to normal : 3.HEAD-amd64-ubuntu-saucy #368
See http://build.squid-cache.org/job/3.HEAD-amd64-ubuntu-saucy/368/changes ___ squid-dev mailing list squid-dev@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-dev
Re: [squid-dev] [PATCH] adapting 100-Continue / A Bug 4067 fix
patch applied to trunk as revno:13697 Regards, Christos On 11/10/2014 12:14 PM, Amos Jeffries wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/11/2014 11:06 p.m., Tsantilas Christos wrote: On 11/10/2014 09:36 AM, Amos Jeffries wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/11/2014 10:02 a.m., Tsantilas Christos wrote: I am re-posting the patch. There are not huge changes. Looking over this in more detail... Whats the point of having buildHttpRequest() a separate method from processRequest() ? It makes the code more readable. It is a private method for use internally by the Http::Server class. I am suggesting to leave it as is. We can fix method name or its documentation. The documentation for buildHttpRequest() is wrong, no parsing takes place there. It is purely post-parse processing of some parsed HTTP request. ie processParsedRequest() action. The HttpRequest::CreateFromUrlAndMethod still does parsing. But yes we are using pre-parsed informations to build HTTP request object. Is it ok the following documentation for buildHttpRequest? /// Handles parsing results and build an error reply if parsing I would say Handles parsing results. May generate then deliver an error reply to the client if parsing To make it clear that actual socket I/O might take place. /// is failed, or parses the url and build the HttpRequest object /// using parsing results. /// Return false if parsing is failed, true otherwise. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUYJAfAAoJELJo5wb/XPRjs58H/3Dya79ljhnSO1H/tuh5aRFI vp9cWogMg6OSZT640JMAxsUqL3SkbskUxj8a7aVP6nBW8Xu2VnFJ3PfEIPhq2l09 CI/wt2erj4iPqabZOhdWxNXBGfrG5t+4qIWZe9ALuXAZsjxAGABWU4Z7tYPn3P7A cGKuwbV/3rWGBiXXJgWZuuQeEmD6+QX2j31ErGCJbvzje1acyLRG8Fo8YABiqE6N jveeTVJ44ktzSmP2Lf9OneTLp5ktrc/vag0N0zLu6qY3xKxix/QuSBH+7Ff88wX8 ehctZxnWwnN41brIoZUXIb9Zhqr7GaJ/qYyjFCmJgyCp/bumfHJV7OIld+v5Pck= =78Lp -END PGP SIGNATURE- ___ squid-dev mailing list squid-dev@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-dev ___ squid-dev mailing list squid-dev@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-dev
[squid-dev] Build failed in Jenkins: 3.HEAD-amd64-centos-7-clang #89
See http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/89/changes Changes: [squid...@squid-cache.org] SourceFormat Enforcement [Christos Tsantilas] Adapting 100-continue Currently squid fails to handle correctly 100 Continue requests/responses when ICAP is used. The problems discussed in squid bugzilla: http://bugs.squid-cache.org/show_bug.cgi?id=4067 A short discussion of the problem: When a data upload request enters squid (eg a PUT request with Expect: 100-continue header), squid sends ICAP headers and HTTP headers to ICAP server and stucks waiting for ever the request body data. This patch implements the force_request_body_continuation access list directive which controls how Squid handles data upload requests from HTTP and send the request body to Squid. An allow match tells Squid to respond with the HTTP 100 or FTP 150 (Please Continue) control message on its own, before forwarding the request to an adaptation service or peer. Such a response usually forces the request sender to proceed with sending the body. A deny match tells Squid to delay that control response until the origin server confirms that the request body is needed. Delaying is the default behavior. This is a Measurement Factory project -- [...truncated 8659 lines...] depbase=`echo tests/stub_http.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_http.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_http.o ../../src/tests/stub_http.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_icp.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_icp.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_icp.o ../../src/tests/stub_icp.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_internal.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_internal.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_internal.o ../../src/tests/stub_internal.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_ipc.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_ipc.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_ipc.o ../../src/tests/stub_ipc.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_ipcache.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\;
[squid-dev] Build failed in Jenkins: 3.HEAD-amd64-centos-7-clang #90
See http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/90/ -- [...truncated 8834 lines...] mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_HelperChildConfig.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_HelperChildConfig.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_HelperChildConfig.o ../../src/tests/stub_HelperChildConfig.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_http.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_http.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_http.o ../../src/tests/stub_http.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_icp.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_icp.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_icp.o ../../src/tests/stub_icp.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_internal.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_internal.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_internal.o ../../src/tests/stub_internal.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_ipc.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_ipc.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_ipc.o ../../src/tests/stub_ipc.cc \ mv -f $depbase.Tpo $depbase.Po depbase=`echo tests/stub_ipcache.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`;\ ccache clang++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc/squid.conf\; -DDEFAULT_SQUID_DATA_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/share\; -DDEFAULT_SQUID_CONFIG_DIR=\http://build.squid-cache.org/job/3.HEAD-amd64-centos-7-clang/ws/btlayer-00-default/squid-3.HEAD-BZR/_inst/etc\; -I../.. -I../../include -I../../lib -I../../src -I../include-I../src -Werror -Qunused-arguments -D_REENTRANT -g -O2 -MT tests/stub_ipcache.o -MD -MP -MF $depbase.Tpo -c -o tests/stub_ipcache.o ../../src/tests/stub_ipcache.cc \ mv -f $depbase.Tpo
Re: [squid-dev] [PATCH] Drop some CbDataList
There seems to be some extraneous code (documentation updates, formatting, etc). Is it intentional? On Mon, Nov 10, 2014 at 2:53 PM, Amos Jeffries squ...@treenet.co.nz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Most of the uses of CbDataList appear to be abusing it for regular list storage without any real need for CBDATA to be involved at all. This replaces several of the simpler uses of CbDataList in favour of std::list. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUYMNwAAoJELJo5wb/XPRjXRoH/jsgFpxVeBauRRhH1Tw8rcQG Y4dQrGPBRZu+OEI9WOyyy5iao0cc13ueSXoW6ppmjCcyEd162bKpvgDOvoCfb2NU lsgwcxpEg0anSSPsA+TaNT7xnC6TB/z1MPMQZRHjzTrP8d9mo/usQdDPvgcEaEl5 hmUXcVrkY4TimkBjLfQnvIUUSEpgsT056PHYQa6vRLEZTPFnE0WlxdwoObV4N76m fjcB7/vyBbuO0JLZOGiW1CABLpu5Cqx69fAtiRan8CIZr2mbNc/wROt9B23hqWg3 aC9sfozmuJUzPebinMyK/J1+EkAjLj/+Wx4FB/swIIVxrAbAnt3hSHdC059NNyU= =8Zfg -END PGP SIGNATURE- ___ squid-dev mailing list squid-dev@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-dev -- Francesco ___ squid-dev mailing list squid-dev@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-dev
[squid-dev] Build failed in Jenkins: 3.HEAD-amd64-OpenBSD-5.4 #215
See http://build.squid-cache.org/job/3.HEAD-amd64-OpenBSD-5.4/215/ -- [...truncated 7001 lines...] ../../src/tests/testHttp1Parser.cc:846: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:860: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:861: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:862: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:863: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:864: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:865: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:866: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:867: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:868: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:869: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:870: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:871: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:872: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:873: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:874: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:875: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:884: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:885: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:886: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:887: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:888: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:889: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:890: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:891: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:892: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:893: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:894: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:895: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:896: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:897: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:898: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:899: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:958: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:959: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:960: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:961: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:962: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:963: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:964: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:965: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:966: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:967: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:968: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:969: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:970: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:971: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:972: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:973: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:996: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:997: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:998: error: expected primary-expression before '.' token
[squid-dev] Build failed in Jenkins: 3.HEAD-amd64-ubuntu-precise #846
See http://build.squid-cache.org/job/3.HEAD-amd64-ubuntu-precise/846/changes Changes: [squid...@squid-cache.org] SourceFormat Enforcement [Christos Tsantilas] Adapting 100-continue Currently squid fails to handle correctly 100 Continue requests/responses when ICAP is used. The problems discussed in squid bugzilla: http://bugs.squid-cache.org/show_bug.cgi?id=4067 A short discussion of the problem: When a data upload request enters squid (eg a PUT request with Expect: 100-continue header), squid sends ICAP headers and HTTP headers to ICAP server and stucks waiting for ever the request body data. This patch implements the force_request_body_continuation access list directive which controls how Squid handles data upload requests from HTTP and send the request body to Squid. An allow match tells Squid to respond with the HTTP 100 or FTP 150 (Please Continue) control message on its own, before forwarding the request to an adaptation service or peer. Such a response usually forces the request sender to proceed with sending the body. A deny match tells Squid to delay that control response until the origin server confirms that the request body is needed. Delaying is the default behavior. This is a Measurement Factory project -- [...truncated 8686 lines...] ../../src/tests/testHttp1Parser.cc:846:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:860:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:861:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:862:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:863:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:864:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:865:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:866:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:867:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:868:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:869:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:870:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:871:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:872:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:873:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:874:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:875:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:884:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:885:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:886:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:887:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:888:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:889:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:890:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:891:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:892:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:893:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:894:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:895:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:896:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:897:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:898:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:899:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:958:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:959:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:960:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:961:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:962:13: error: expected primary-expression before ‘.’ token
Re: [squid-dev] [PATCH] Drop some CbDataList
On 11/10/2014 03:53 PM, Amos Jeffries wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Most of the uses of CbDataList appear to be abusing it for regular list storage without any real need for CBDATA to be involved at all. +1 This replaces several of the simpler uses of CbDataList in favour of std::list. Amos ___ squid-dev mailing list squid-dev@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-dev
Re: [squid-dev] Build failed in Jenkins: 3.HEAD-amd64-ubuntu-precise #844
root@rs-ubuntu-precise:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.5 LTS Release:12.04 Codename: precise root@rs-ubuntu-precise:~# gcc --version gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 On Mon, Nov 10, 2014 at 11:50 AM, Amos Jeffries squ...@treenet.co.nz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/11/2014 11:23 p.m., n...@squid-cache.org wrote: See http://build.squid-cache.org/job/3.HEAD-amd64-ubuntu-precise/844/changes snip -- [...truncated 8681 lines...] ../../src/tests/testHttp1Parser.cc:846:13: error: expected primary-expression before '.' token This looks like the Precise test node needs to be upgraded to the latest version of Precise. 12.04.5 is supposed to have GCC 4.6 which should be able to handle initializer lists. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUYJiLAAoJELJo5wb/XPRj+9QIANXXJN+ZJFaGTAAHykQpxaP+ BVrL4N2HtlJhlLhoiQzr+srG0JVdDsO6t7EfuJXYQyVkgOALzmVUUmCamWP+g7Og yQtD5M1mQbquPyCwZlNXru4HhKvVLr7vl+VMVmEq/WK2VzS1cvjwBUF6FW9HrVo8 YO2s4FmtZK1DOaLbVgjzKalbgQQiotacBUnZceZ0o3Mn1Vm30nZ1Tnr2YIz74zbd 9XAOGBoY9/4mkJv4JrX91j4B9jAzYNiNpVx1sjCfh27FXDgRHj2b3xz+RKt2sFbB ZroKyzf7fV6N+wo7kedk7SY3OdKGbqPAwPVyDnbO297WOos/UTAAaR9G71VvxHY= =PRyM -END PGP SIGNATURE- ___ squid-dev mailing list squid-dev@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-dev -- Francesco ___ squid-dev mailing list squid-dev@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-dev
[squid-dev] Build failed in Jenkins: 3.HEAD-amd64-OpenBSD-5.4 #216
See http://build.squid-cache.org/job/3.HEAD-amd64-OpenBSD-5.4/216/changes Changes: [Amos Jeffries] Fix segmentation fault in ACLUrlPathStrategy::match CONNECT requests do not contain a path segment. If tested with a urlpath_regex ACL will crash Squid via xstrdup() NULL protection. -- [...truncated 7003 lines...] ../../src/tests/testHttp1Parser.cc:846: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:860: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:861: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:862: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:863: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:864: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:865: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:866: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:867: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:868: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:869: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:870: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:871: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:872: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:873: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:874: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:875: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:884: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:885: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:886: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:887: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:888: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:889: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:890: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:891: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:892: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:893: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:894: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:895: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:896: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:897: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:898: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:899: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:958: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:959: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:960: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:961: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:962: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:963: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:964: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:965: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:966: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:967: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:968: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:969: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:970: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:971: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:972: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:973: error: expected primary-expression before '.' token ../../src/tests/testHttp1Parser.cc:996: error: expected primary-expression before
[squid-dev] Build failed in Jenkins: 3.HEAD-amd64-ubuntu-precise #848
See http://build.squid-cache.org/job/3.HEAD-amd64-ubuntu-precise/848/changes Changes: [Amos Jeffries] Fix segmentation fault in ACLUrlPathStrategy::match CONNECT requests do not contain a path segment. If tested with a urlpath_regex ACL will crash Squid via xstrdup() NULL protection. -- [...truncated 8678 lines...] ../../src/tests/testHttp1Parser.cc:846:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:860:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:861:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:862:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:863:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:864:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:865:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:866:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:867:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:868:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:869:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:870:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:871:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:872:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:873:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:874:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:875:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:884:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:885:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:886:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:887:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:888:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:889:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:890:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:891:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:892:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:893:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:894:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:895:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:896:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:897:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:898:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:899:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:958:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:959:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:960:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:961:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:962:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:963:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:964:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:965:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:966:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:967:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:968:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:969:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:970:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:971:13: error: expected primary-expression before ‘.’ token ../../src/tests/testHttp1Parser.cc:972:13: error: expected primary-expression before ‘.’ token
Re: [squid-dev] Squid-3.5 release countdown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/11/2014 6:12 a.m., Eliezer Croitoru wrote: Just to make sure... I will try to build this week the 3.5 2 beta as a RPM since the 3.4.9 is now on the countdown release(exit 0 and needs more testing). What about the open bugs at the 3.4 in general? Do we expect to fix most of them for 3.5 stable? Bugs in older versions are of course attempted to be fixed, but do not hold up the release. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUYcDrAAoJELJo5wb/XPRjD/oH/3weJCC6wwa9IzcPnk8OHFss DWkPTWmcW0or1nwtP5RYOO1BBSqs3KCMq+V/V8IgADheHnJKXA/oF4WNRpN0HQs0 StvoYuqXwDKSHDcD/RtUsk5RHELMzKggfZT/7caunH9hkF2w69Au4szIPPgaOpcm 6tmqCGg97f7Ib9EJNXosVzELK9oeqzFcVszSLFnwOz5ViXMxCDxWrQ3uks/BgSlz ayaYVrMp9DWwfxdk5ARLNAmelgY4nztkAa6HFGJE3KNaMtb+lFPJNL+Kwk0uzDLC 0x27EjZGvbhWDbI0AukVQJTDwZb2JYSaNHG8gybttnRXiPVKLB9rYXKOT7uh2EA= =CGGU -END PGP SIGNATURE- ___ squid-dev mailing list squid-dev@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-dev
