kloczek
commented
3 years ago Closed kloczek closed 3 years ago
kloczek
commented
3 years ago 
michaelrsweet
commented
3 years ago You have another process (maybe a previous instance of the test server) still running.
kloczek
commented
3 years ago Not possible beacuse I'm running build process (which exrcution of the test suite is is part) in fresh dedicated system.
Because I'm running test suite in parallel (-j48) onl;y possibility is that some test units started in parallel are disturbing each other.
Will try to force -j1.
michaelrsweet
commented
3 years ago @kloczek This test suite is run for every commit via Github Actions on macOS and Ubuntu, and I am not seeing this error there (nor on my local machines).
The error does happen if there is another process listening on port 8631, usually if you have an old test server still running.
kloczek
commented
3 years ago Do you run test suite with -jN?
michaelrsweet
commented
3 years ago @kloczek No, but it won't matter because the test target won't be run in parallel:
#
# Don't run top-level build targets in parallel...
#
.NOTPARALLEL:In the far distant past (18? years ago) I used to run the test suite on multiple physical systems with different OS's, and there I used -jN to speed up the builds. The .NOTPARALLEL directive was added back then to ensure that the test suite wasn't run in parallel with anything else (not that there are any other tests that bind to port 8631...) There is also support for using a different port number for each build (which I used when running multiple CI jobs in parallel with different configurations) - just set the CUPS_TESTPORT environment variable to override the default value of 8631.
kloczek
commented
3 years ago That is OK however as I wrote I have nothing listening on that port :/
I've started one more time check however it takes very long time (about hour) to finish.
kloczek
commented
3 years ago I've started test ubiut 5 hour ago and still is not finished. That is th elongest (and still not finished) part of the test suite:
Running IPP compliance tests...
Performing 4.1-requests.test: PASS
Performing 4.2-cups-printer-ops.test: PASS
Performing 4.3-job-ops.test: PASS
Performing 4.4-subscription-ops.test: PASS
Performing ipp-2.1.test: PASS
Running command tests...
Performing 5.1-lpadmin.sh: PASS
Waiting for jobs to complete...1...
Performing 5.2-lpc.sh: PASS
Waiting for jobs to complete...1...
Performing 5.3-lpq.sh: PASS
Waiting for jobs to complete...1...
Performing 5.4-lpstat.sh: PASS
Waiting for jobs to complete...1...Nothing more than test sute litener is tarted:
[tkloczko@barrel SPECS]$ sudo netstat -anlp | grep 8631
tcp 0 0 127.0.0.1:8631 0.0.0.0:* LISTEN 2925735/../schedule
tcp6 0 0 ::1:8631 :::* LISTEN 2925735/../scheduleJust found in th test suite output:
If CUPS was built with the --enable-debug-printfs configure option, you
can enable debug logging of the libraries.
Enter Y or a number from 0 to 9 to enable debug logging or N to not: [N]
Creating directories for test...
mkdir: cannot create directory '/tmp/cups-tkloczko/share/locale/en': File exists <<<< HERE
ln: failed to create symbolic link '/tmp/cups-tkloczko/share/locale/en/cups_en.po': File exists <<<< HERE
Creating cupsd.conf for test...
Creating printers.conf for test...
Setting up environment variables for test...
Creating wrapper script...
Starting scheduler:
/tmp/cups-tkloczko/runcups ../scheduler/cupsd -c /tmp/cups-tkloczko/cupsd.conf -f >/tmp/cups-tkloczko/log/debug_log 2>&1 &
Scheduler is PID 2925735.