Re: [ns] ns-2.34 validation tests fail (64bit-processor)
On 08/08/2012 11:38 PM, Behnaz Bostanipour wrote: Hello, I successfuly installed ns2.34 on a MacOS(Lion). My Mac is a (Core i7-64bit processor). When I execute "./validate" and these tests fail: (snip) I was finally able to get ns-allinone-2.35 to build on my 64-bit OS X Mountain Lion machine (details are in another message). After doing so and running the validate script, no errors were reported. I don't have a Lion server around since it was upgraded to Mountain Lion, but I remember trying this on Lion a while back and not finding errors. So, I am curious as to why your system sees errors in some tests. Could you please try to run through the following steps, and if errors are reported, send me the ns-2.35 config.log and the validation report of which tests still fail? (or where the build fails, if you can't build) start with fresh copy of ns-allinone-2.35.tar.bz2 apply the attached patch: # cd ns-allinone-2.35 # patch -p1 -i install.osx.patch # ./install (if everything builds successfully) # cd ns-2.35 # ./validate >& my.validate.out
Re: [ns] ns-2.34 validation tests fail (64bit-processor)
On 2012-08-30 08:29, Behnaz Bostanipour wrote: > Hello Tom, > > Thanks for your reply. I put some comments on your email below: > > > On 30 août 2012, at 16:13, Tom Henderson wrote: > >> >> On 08/29/2012 06:50 AM, behnaz.bostanip...@unil.ch wrote: I'm not able to reproduce that error, so I would like to see some examples of the diffed output. Would you mind collecting all of the *.test output files for the tests that failed and send them to me in a tarball, such as: cd tcl/tests find . -name "*.test" -type f | xargs tar cvfj ns-2-diffs.tbz2 and send me the ns-2-diffs.tbz2 file? Thanks, Tom >>> >>> >>> Here you are, I exactly execuuted your command, but not sure >>> if it has all the outputs that we want (i.e., for tests: >>> "test-all-tcpLinux", "test-all-tcpHighspeed", "test-all-red" >>> and "test-all-cbq". >>> >> >> There seem to be a few things going on here. >> >> for the test-all-cbq and test-all-red files, the data seems correct >> but >> the formatting is slightly off: there are commas for periods in >> some of >> the outputs. e.g. >> >> test-output-red/flows-combined.test >>> ==> flows_combined.test <== >>> TitleText: test_flows_combined >>> Device: Postscript >>> >>> "flow 1 >>> 84,8786 74,1902 >>> 48,3181 46,8733 >> >> vs. test-output-red/flows-combined (good output) >>> TitleText: test_flows_combined >>> Device: Postscript >>> >>> "flow 1 >>> 84.8786 74.1902 >>> 48.3181 46.8733 >> >> >> This may have something to do with the version of xgraph on the >> system. > > Yes, if you look at the validation output, whenever a test fails , it > says: > >> > "couldn't execute "xgraph": no such file or directory" > > > So, maybe I should do something about my graph, (e.g., reinstall it > or …, do you have any suggestions?) xgraph is an optional component, so I think you could safely ignore that warning. > > >> >> for the tcpLinux and tcpHighspeed tests, there are lines missing >> (either >> truncated, or interleaved in the test output) from the output when >> compared to the reference output. I don't know whether this is >> again a >> post-processing error or whether the simulation is not producing the >> same data. >> >> The test-output-xcp data is different: >> >> 0.12186 420 >> 0.12186 420 >> 0.12186 420 >> 0.12228 8 >> 0.12228 8 >> >> vs >> >> 0.12186 420 >> 0.12186 420 >> 0.12186 420 >> 0.12228 819 >> 0.12228 819 >> >> In summary, I would be suspicious of the use of the tcpLinux, >> tcpHighspeed, and xcp models on this platform. To debug this >> probably >> requires to step through the code at the points where the output >> diverge, using also a platform such as Linux that produces the >> reference >> output. >> >> I don't have ns-2 running on Mountain Lion yet but I'll check >> whether >> similar issues arise there. >> >> - Tom >> >> > > As I explained in my last email, I would like to do some simulations > for IEEE 802.11 MAC layer and also use some routing protocols , I > don't think that validation tests failures for TCP will not be a > problem, my only concern is that these tests fail: > > /test-all-red ./test-all-cbq > > Do you think that will cause a problem for my simulations if I these > models do not work properly on my machine? > Based on what you sent, the models appear to be working properly and the difference is due to the post-processing for the regression tests. - Tom
Re: [ns] ns-2.34 validation tests fail (64bit-processor)
Hello Tom, Thanks for your reply. I put some comments on your email below: On 30 août 2012, at 16:13, Tom Henderson wrote: > > On 08/29/2012 06:50 AM, behnaz.bostanip...@unil.ch wrote: >>> I'm not able to reproduce that error, so I would like to >>> see some examples of the diffed output. Would you mind >>> collecting all of the *.test output files for the tests >>> that failed and send them to me in a tarball, such as: >>> >>> cd tcl/tests >>> find . -name "*.test" -type f | xargs tar cvfj >>> ns-2-diffs.tbz2 >>> >>> and send me the ns-2-diffs.tbz2 file? >>> >>> Thanks, >>> Tom >> >> >> Here you are, I exactly execuuted your command, but not sure >> if it has all the outputs that we want (i.e., for tests: >> "test-all-tcpLinux", "test-all-tcpHighspeed", "test-all-red" >> and "test-all-cbq". >> > > There seem to be a few things going on here. > > for the test-all-cbq and test-all-red files, the data seems correct but > the formatting is slightly off: there are commas for periods in some of > the outputs. e.g. > > test-output-red/flows-combined.test >> ==> flows_combined.test <== >> TitleText: test_flows_combined >> Device: Postscript >> >> "flow 1 >> 84,8786 74,1902 >> 48,3181 46,8733 > > vs. test-output-red/flows-combined (good output) >> TitleText: test_flows_combined >> Device: Postscript >> >> "flow 1 >> 84.8786 74.1902 >> 48.3181 46.8733 > > > This may have something to do with the version of xgraph on the system. Yes, if you look at the validation output, whenever a test fails , it says: > > "couldn't execute "xgraph": no such file or directory" So, maybe I should do something about my graph, (e.g., reinstall it or …, do you have any suggestions?) > > for the tcpLinux and tcpHighspeed tests, there are lines missing (either > truncated, or interleaved in the test output) from the output when > compared to the reference output. I don't know whether this is again a > post-processing error or whether the simulation is not producing the > same data. > > The test-output-xcp data is different: > > 0.12186 420 > 0.12186 420 > 0.12186 420 > 0.12228 8 > 0.12228 8 > > vs > > 0.12186 420 > 0.12186 420 > 0.12186 420 > 0.12228 819 > 0.12228 819 > > In summary, I would be suspicious of the use of the tcpLinux, > tcpHighspeed, and xcp models on this platform. To debug this probably > requires to step through the code at the points where the output > diverge, using also a platform such as Linux that produces the reference > output. > > I don't have ns-2 running on Mountain Lion yet but I'll check whether > similar issues arise there. > > - Tom > > As I explained in my last email, I would like to do some simulations for IEEE 802.11 MAC layer and also use some routing protocols , I don't think that validation tests failures for TCP will not be a problem, my only concern is that these tests fail: /test-all-red ./test-all-cbq Do you think that will cause a problem for my simulations if I these models do not work properly on my machine? Thanks, Behnaz
Re: [ns] ns-2.34 validation tests fail (64bit-processor)
On 08/30/2012 07:13 AM, Tom Henderson wrote: > On 08/29/2012 06:50 AM, behnaz.bostanip...@unil.ch wrote: >>> I'm not able to reproduce that error, so I would like to >>> see some examples of the diffed output. Would you mind >>> collecting all of the *.test output files for the tests >>> that failed and send them to me in a tarball, such as: >>> >>> cd tcl/tests >>> find . -name "*.test" -type f | xargs tar cvfj >>> ns-2-diffs.tbz2 >>> >>> and send me the ns-2-diffs.tbz2 file? >>> >>> Thanks, >>> Tom >> >> >> Here you are, I exactly execuuted your command, but not sure >> if it has all the outputs that we want (i.e., for tests: >> "test-all-tcpLinux", "test-all-tcpHighspeed", "test-all-red" >> and "test-all-cbq". >> > > There seem to be a few things going on here. > > for the test-all-cbq and test-all-red files, the data seems correct but > the formatting is slightly off: there are commas for periods in some of > the outputs. e.g. > > test-output-red/flows-combined.test >> ==> flows_combined.test <== >> TitleText: test_flows_combined >> Device: Postscript >> >> "flow 1 >> 84,8786 74,1902 >> 48,3181 46,8733 > > vs. test-output-red/flows-combined (good output) >> TitleText: test_flows_combined >> Device: Postscript >> >> "flow 1 >> 84.8786 74.1902 >> 48.3181 46.8733 > > > This may have something to do with the version of xgraph on the system. actually, xgraph is not used to generate this data; it is probably some divergence in the output of getrc or raw2xg, such as: exec $PERL ../../bin/getrc -s 2 -d 3 out.tr | \ $PERL ../../bin/raw2xg -s 0.01 -m 90 -t $tname > temp.rands
Re: [ns] ns-2.34 validation tests fail (64bit-processor)
On 08/29/2012 06:50 AM, behnaz.bostanip...@unil.ch wrote: >> I'm not able to reproduce that error, so I would like to >> see some examples of the diffed output. Would you mind >> collecting all of the *.test output files for the tests >> that failed and send them to me in a tarball, such as: >> >> cd tcl/tests >> find . -name "*.test" -type f | xargs tar cvfj >> ns-2-diffs.tbz2 >> >> and send me the ns-2-diffs.tbz2 file? >> >> Thanks, >> Tom > > > Here you are, I exactly execuuted your command, but not sure > if it has all the outputs that we want (i.e., for tests: > "test-all-tcpLinux", "test-all-tcpHighspeed", "test-all-red" > and "test-all-cbq". > There seem to be a few things going on here. for the test-all-cbq and test-all-red files, the data seems correct but the formatting is slightly off: there are commas for periods in some of the outputs. e.g. test-output-red/flows-combined.test > ==> flows_combined.test <== > TitleText: test_flows_combined > Device: Postscript > > "flow 1 > 84,8786 74,1902 > 48,3181 46,8733 vs. test-output-red/flows-combined (good output) > TitleText: test_flows_combined > Device: Postscript > > "flow 1 > 84.8786 74.1902 > 48.3181 46.8733 This may have something to do with the version of xgraph on the system. for the tcpLinux and tcpHighspeed tests, there are lines missing (either truncated, or interleaved in the test output) from the output when compared to the reference output. I don't know whether this is again a post-processing error or whether the simulation is not producing the same data. The test-output-xcp data is different: 0.12186 420 0.12186 420 0.12186 420 0.12228 8 0.12228 8 vs 0.12186 420 0.12186 420 0.12186 420 0.12228 819 0.12228 819 In summary, I would be suspicious of the use of the tcpLinux, tcpHighspeed, and xcp models on this platform. To debug this probably requires to step through the code at the points where the output diverge, using also a platform such as Linux that produces the reference output. I don't have ns-2 running on Mountain Lion yet but I'll check whether similar issues arise there. - Tom
Re: [ns] ns-2.34 validation tests fail (64bit-processor)
Respected Sir My self vipul kumar and i am LINUX user I got you email ID fromYoutube video, as there in video i have seen you expertes in NS. so kindly help me in simulating TCP/IP i will be very thank full to you You'r truely vipul kumar :) www.vipullinux.wordpress.com On Wed, Aug 29, 2012 at 7:20 PM, wrote: > > > > I'm not able to reproduce that error, so I would like to > > see some examples of the diffed output. Would you mind > > collecting all of the *.test output files for the tests > > that failed and send them to me in a tarball, such as: > > > > cd tcl/tests > > find . -name "*.test" -type f | xargs tar cvfj > > ns-2-diffs.tbz2 > > > > and send me the ns-2-diffs.tbz2 file? > > > > Thanks, > > Tom > > > Here you are, I exactly execuuted your command, but not sure > if it has all the outputs that we want (i.e., for tests: > "test-all-tcpLinux", "test-all-tcpHighspeed", "test-all-red" > and "test-all-cbq". > > So please let me know if you need other outputs, > Thanks, > Behnaz > >
Re: [ns] ns-2.34 validation tests fail (64bit-processor)
On 29 août 2012, at 15:00, Tom Henderson wrote: > > Could you please send the full validate output? It seems like the file you > sent is truncated at 2204 lines. > Thanks for your reply. I opened this one in my texShop and it has 7167 lines. Best, Behnaz
Re: [ns] ns-2.34 validation tests fail (64bit-processor)
On 08/09/2012 08:59 AM, behnaz.bostanip...@unil.ch wrote: > Hi, > > Thanks for your reply. I installed ns2.35 and actually the > majority of these problems are solved. But still these tests > fail: > > validate overall report: some tests failed: > ./test-all-tcpLinux ./test-all-tcpHighspeed > /test-all-red ./test-all-cbq > > > whith a closer look I noticed this error message for these > tests: > > "couldn't execute "xgraph": no such file or directory" This shouldn't cause validation errors. I don't have a 10.7 64-bit test machine at my disposal so I can't try to reproduce at the moment. I have 10.6.8 32-bit machine which doesn't exhibit that. I also have a newly-upgraded 10.8 64-bit machine, but there are other issues related to X11 changes in Mountain Lion that, for now, are blocking me to test it there. Anyway, I would suggest to send to me or post to the tracker [*] the output of this: ./validate >& validate.log so that someone can look at the specific errors reported. If you aren't using these specific models in your work, you have less to worry about. - Tom [*] http://sourceforge.net/tracker/?group_id=149743&atid=775392
[ns] ns-2.34 validation tests fail (64bit-processor)
Hello, I successfuly installed ns2.34 on a MacOS(Lion). My Mac is a (Core i7-64bit processor). When I execute "./validate" and these tests fail: validate overall report: some portable tests failed: ./test-all-newreno ./test-all-sack ./test-all-tcpOptions ./test-all-tcpLinux ./test-all-tcpHighspeed ./test-all-red ./test-all-cbq ./test-all-webtraf some non-portable tests also failed: ./test-all-srm ./test-all-smac-multihop ./test-all-hier-routing ./test-all-algo-routing ./test-all-mcast ./test-all-vc ./test-all-session ./test-all-mixmode ./test-all-webcache ./test-all-mcache ./test-all-plm ./test-all-wireless-tdma to re-run a specific test, cd tcl/test; ./test-all-TEST-NAME Do you know what should I do? I read in the official Nsnam Troubleshooting page that “ns-2 is known to have problems with some validation tests on certain platforms due to 64-bit problems”. I am not sure if theses tests fail because of the 64-bit processor but if it's the case is there a solution? Thanks in advance for your reply.
