Changeset 1f0e7ec for networking/netlibs/curl.xml
- Timestamp:
- 03/27/2023 08:14:08 PM (13 months ago)
- Branches:
- 12.0, 12.1, kea, ken/TL2024, ken/tuningfonts, lazarus, lxqt, plabs/newcss, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/xf86-video-removal
- Children:
- fd52540
- Parents:
- afb71d0a
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
networking/netlibs/curl.xml
rafb71d0a r1f0e7ec 7 7 <!ENTITY curl-download-http "https://curl.se/download/curl-&curl-version;.tar.xz"> 8 8 <!ENTITY curl-download-ftp " "> 9 <!ENTITY curl-md5sum " 8bea0c58428578f397471fe209fad6ab">9 <!ENTITY curl-md5sum "f6c2fdeb30ad30234378a56c28350845"> 10 10 <!ENTITY curl-size "2.5 MB"> 11 <!ENTITY curl-buildsize " 150 MB (add 23MB for tests)">12 <!ENTITY curl-time "0. 2 SBU (with parallelism=4; add 16 SBU for tests)">11 <!ENTITY curl-buildsize "45 MB (add 19 MB for tests)"> 12 <!ENTITY curl-time "0.3 SBU (with parallelism=4; add 16 SBU for tests (without valgrind, add 35 SBU with valgrind)"> 13 13 ]> 14 14 … … 123 123 tests completed happily without it, although the test for unit1323 124 124 reported that the tool set in the test case does not exist - ken --> 125 <xref linkend="stunnel"/> (for the HTTPS and FTPS tests) and 125 <xref linkend="httpd"/> and 126 <xref linkend="stunnel"/> (for the HTTPS and FTPS tests), and 126 127 <xref linkend="valgrind"/> (this will slow the tests down and may cause failures.) 127 128 </para> … … 363 364 TESTDONE: 1342 tests out of 1342 reported OK: 100% 364 365 libssh2 installed and enabled 366 367 [renodr] - Test results for 8.0.1 (2023-03-27) 368 TESTDONE: 1593 tests were considered during 4761 seconds. 369 TESTDONE: 1356 tests out of 1356 reported OK: 100% 370 All BLFS dependencies installed. 371 Note that if I move /usr/bin/valgrind to a place where it can't be found, I get 372 TESTDONE: 1593 tests were considered during 595 seconds. 373 TESTDONE: 1356 tests out of 1356 reported OK: 100% 374 It appears that every test is now run under valgrind. 365 375 --> 366 376 … … 380 390 381 391 <para> 382 Simple tests to the new installed <command>curl</command>: 392 To run some simple verification tests on the newly installed 393 <command>curl</command>, issue the following commands: 383 394 <command>curl --trace-ascii debugdump.txt https://www.example.com/</command> 384 395 and 385 396 <command>curl --trace-ascii d.txt --trace-time https://example.com/</command>. 386 397 Inspect the locally created trace files <filename>debugdump.txt</filename> 387 and <filename>d.txt</filename>, which contain version downloaded388 files information, etc. One file has the time for each action logged.398 and <filename>d.txt</filename>, which contains version information, 399 downloaded files information, etc. One file has the time for each action logged. 389 400 </para> 390 401 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.