Bug 324250 - ktcpsockettest tests network connectivity to iana.org
Summary: ktcpsockettest tests network connectivity to iana.org
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: knetwork (show other bugs)
Version: 4.10.5
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL: http://www.iana.org
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-30 04:04 UTC by Christopher Yeleighton
Modified: 2023-01-03 11:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Consider that a socket need not be connected and it is not KDE’s fault (7.48 KB, patch)
2013-08-30 22:21 UTC, Christopher Yeleighton 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Yeleighton 2013-08-30 04:04:40 UTC 
ktcpsockettest tests network connectivity to iana.org.  This is inappropriate; if the test fails, KDE can do nothing to fix the failure.

Reproducible: Always

Steps to Reproduce:
  1. /home/abuild/rpmbuild/BUILD/kdelibs-4.10.5/build/kdecore/tests/ktcpsockettest.shell

Actual Results:  
  1. 
44: FAIL!  : KTcpSocketTest::statesIana() Compared values are not the same
44:    Actual (s->state()): UnconnectedState
44:    Expected (KTcpSocket::ConnectedState): ConnectedState
44:    Loc: [/home/abuild/rpmbuild/BUILD/kdelibs-4.10.5/kdecore/tests/ktcpsockettest.cpp(236)]


Expected Results:  
  1.

Actual results after Bug 324231 has been fixed.
Comment 1 Christopher Yeleighton 2013-08-30 04:15:52 UTC 
Oh, and besides, the test should report the actual reason for the failure, e.g.: unknown host www.iana.org.
Comment 2 Christopher Yeleighton 2013-08-30 18:34:57 UTC 
And besides, we could DDOS iana.org this way.  Why not use kde.org instead?
Comment 3 Christopher Yeleighton 2013-08-30 21:24:57 UTC 
Why do you think that KTcpSocket should be in ConnectingState immediately after connectToHost?  That is expected only if the previous lookup for the same host succeeded.
Comment 4 Christopher Yeleighton 2013-08-30 22:21:04 UTC 
Created attachment 82044 [details]
Consider that a socket need not be connected and it is not KDE’s fault
Comment 5 Andrew Crouthamel 2018-11-10 03:11:58 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-11-20 03:59:34 UTC 
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Justin Zobel 2022-12-31 00:24:33 UTC 
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!