Status: Accepted
Owner: [hidden email] Labels: Type-Bug Target-Zinc Milestone-2.0 New issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629 https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/200/ fail most probably because we run two image at the same time on the same machine. Increasing the port number might solve the issue of failing tests. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Status: FixReviewNeeded Comment #1 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629 Name: SLICE-Issue-7629-Add-more-Port-variation-for-the-ZincServer-tests-CamilloBruni.1 Author: CamilloBruni Time: 1 March 2013, 6:12:02.008 pm UUID: c03e7f50-ed98-46db-9137-a592358723e8 Ancestors: Dependencies: Zinc-Tests-CamilloBruni.177 increas port variation to 100 for ZnServer tests -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Status: MonkeyIsChecking Comment #2 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629#c2 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Status: FixReviewNeeded Comment #3 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629 Name: SLICE-Issue-7629-Add-more-Port-variation-for-the-ZincServer-tests-CamilloBruni.2 Author: CamilloBruni Time: 1 March 2013, 6:15:34.43 pm UUID: 988a92b9-53ed-45bc-a3fe-1f9e52a63947 Ancestors: SLICE-Issue-7629-Add-more-Port-variation-for-the-ZincServer-tests-CamilloBruni.1 Dependencies: Zinc-Tests-CamilloBruni.178 fixed some more places the rely on the a random server port number -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Status: MonkeyIsChecking Comment #4 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629#c4 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Status: ValidatedByTheMonkey Labels: CheckedIn20579 Comment #5 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629#c5 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Status: FixToInclude Comment #6 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #7 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629 Right, I understand but it remains a hack: the ports will sometimes collide no matter what we do randomly. We have to think about a better solution. And it is very hard to test reliably if a port is in use. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #8 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629 with our new jenkins setup we could basically eliminate that issue by creating enough single job slaves ;) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #9 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629 Another negative consequence of extending the range is that right now, the Zn tests need the range 1701 to 1710 be be free, because any of these ports might be needed - extending this to 1701 to 1800 requires more ports to be free, hence increasing the chance of a conflict with services already in existence. Do you still need this change ? Should I incorporate it upstream ? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #10 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629 well jenkins is doing more or less fine for now: https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/ I added a nasty bash script that delays the execution and thus minimizes the changes that tests run at the same time: sleep $[ $EXECUTOR_NUMBER * 40 ]s Does it have to be a low-range port? I thought the high-range ports are more often free to use. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #11 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629 So it is OK without your changes or do you need them ? The port can be any number only the ports below 1024 are reserved for system usage. Zn traditionally used 1701 as a reference to http://en.wikipedia.org/wiki/USS_Enterprise_(NCC-1701) If the image would know the unique build number, we could of course use that to make sure there cannot be conflicts. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Status: WorkNeeded-Conclusion Comment #12 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Status: Invalid Comment #13 on issue 7629 by [hidden email]: Add more Port variation for the ZincServer tests http://code.google.com/p/pharo/issues/detail?id=7629 Solution: solve with tons of single-slot slaves ;) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Free forum by Nabble | Edit this page |