Hi Yang,
> Failure of test #56 on IRIX 6.2 MIPS C 6.2 autobuilds has always been
> somewhat random. The failure could appear or disappear when some new
> code was commited to CVS. This has always puzzled me, since many times
> the code changed didn't seem to have much to do with that specific
> test case.
I believe something with CVS itself goes wrong sometimes; I've seen that a couple of times now;
and just again after you have modified the bunch of tests when I did a 'cvs update':

P CHANGES
P RELEASE-NOTES
M ares/Makefile.netware
P include/curl/curl.h
M lib/Makefile.netware
P lib/connect.c
P lib/progress.c
P lib/select.c
P lib/ssh.c
P tests/ftpserver.pl
P tests/data/test100
cvs update: checksum failure after patch to tests/data/test100; will refetch
P tests/data/test102
cvs update: checksum failure after patch to tests/data/test102; will refetch
U tests/data/test105
P tests/data/test109
cvs update: checksum failure after patch to tests/data/test109; will refetch
P tests/data/test110
cvs update: checksum failure after patch to tests/data/test110; will refetch
P tests/data/test111
cvs update: checksum failure after patch to tests/data/test111; will refetch
P tests/data/test112
cvs update: checksum failure after patch to tests/data/test112; will refetch
P tests/data/test113
cvs update: checksum failure after patch to tests/data/test113; will refetch
P tests/data/test114
cvs update: checksum failure after patch to tests/data/test114; will refetch
P tests/data/test115
cvs update: checksum failure after patch to tests/data/test115; will refetch
P tests/data/test116
cvs update: checksum failure after patch to tests/data/test116; will refetch
P tests/data/test117
cvs update: checksum failure after patch to tests/data/test117; will refetch
P tests/data/test118
cvs update: checksum failure after patch to tests/data/test118; will refetch
P tests/data/test119
cvs update: checksum failure after patch to tests/data/test119; will refetch
P tests/data/test120
cvs update: checksum failure after patch to tests/data/test120; will refetch
P tests/data/test122
cvs update: checksum failure after patch to tests/data/test122; will refetch
P tests/data/test124
cvs update: checksum failure after patch to tests/data/test124; will refetch
P tests/data/test125
cvs update: checksum failure after patch to tests/data/test125; will refetch
P tests/data/test126
cvs update: checksum failure after patch to tests/data/test126; will refetch
P tests/data/test130
cvs update: checksum failure after patch to tests/data/test130; will refetch
P tests/data/test131
cvs update: checksum failure after patch to tests/data/test131; will refetch
P tests/data/test132
cvs update: checksum failure after patch to tests/data/test132; will refetch
P tests/data/test133
cvs update: checksum failure after patch to tests/data/test133; will refetch
P tests/data/test134
cvs update: checksum failure after patch to tests/data/test134; will refetch
P tests/data/test137
cvs update: checksum failure after patch to tests/data/test137; will refetch
P tests/data/test138
cvs update: checksum failure after patch to tests/data/test138; will refetch
P tests/data/test144
cvs update: checksum failure after patch to tests/data/test144; will refetch
P tests/data/test145
cvs update: checksum failure after patch to tests/data/test145; will refetch
P tests/data/test147
cvs update: checksum failure after patch to tests/data/test147; will refetch
P tests/data/test148
cvs update: checksum failure after patch to tests/data/test148; will refetch
P tests/data/test190
cvs update: checksum failure after patch to tests/data/test190; will refetch
P tests/data/test195
cvs update: checksum failure after patch to tests/data/test195; will refetch
P tests/data/test196
cvs update: checksum failure after patch to tests/data/test196; will refetch
P tests/data/test211
cvs update: checksum failure after patch to tests/data/test211; will refetch
P tests/data/test212
cvs update: checksum failure after patch to tests/data/test212; will refetch
P tests/data/test227
cvs update: checksum failure after patch to tests/data/test227; will refetch
P tests/data/test228
cvs update: checksum failure after patch to tests/data/test228; will refetch
P tests/data/test229
cvs update: checksum failure after patch to tests/data/test229; will refetch
P tests/data/test235
cvs update: checksum failure after patch to tests/data/test235; will refetch
P tests/data/test236
cvs update: checksum failure after patch to tests/data/test236; will refetch
P tests/data/test237
cvs update: checksum failure after patch to tests/data/test237; will refetch
P tests/data/test238
cvs update: checksum failure after patch to tests/data/test238; will refetch
P tests/data/test250
cvs update: checksum failure after patch to tests/data/test250; will refetch
P tests/data/test252
cvs update: checksum failure after patch to tests/data/test252; will refetch
P tests/data/test254
cvs update: checksum failure after patch to tests/data/test254; will refetch
P tests/data/test261
cvs update: checksum failure after patch to tests/data/test261; will refetch
P tests/data/test280
cvs update: checksum failure after patch to tests/data/test280; will refetch
P tests/data/test290
cvs update: checksum failure after patch to tests/data/test290; will refetch
P tests/data/test302
P tests/data/test305
P tests/data/test400
cvs update: checksum failure after patch to tests/data/test400; will refetch
P tests/data/test402
cvs update: checksum failure after patch to tests/data/test402; will refetch
P tests/data/test511
cvs update: checksum failure after patch to tests/data/test511; will refetch
P tests/data/test520
cvs update: checksum failure after patch to tests/data/test520; will refetch
P tests/data/test521
cvs update: checksum failure after patch to tests/data/test521; will refetch
P tests/data/test526
cvs update: checksum failure after patch to tests/data/test526; will refetch
P tests/data/test527
cvs update: checksum failure after patch to tests/data/test527; will refetch
P tests/data/test528
cvs update: checksum failure after patch to tests/data/test528; will refetch
P tests/data/test530
cvs update: checksum failure after patch to tests/data/test530; will refetch
P tests/data/test532
cvs update: checksum failure after patch to tests/data/test532; will refetch
P tests/data/test533
cvs update: checksum failure after patch to tests/data/test533; will refetch
P tests/data/test534
cvs update: checksum failure after patch to tests/data/test534; will refetch
P tests/data/test538
cvs update: checksum failure after patch to tests/data/test538; will refetch
cvs client: refetching unpatchable files
cvs update: warning: `tests/data/test100' was lost
U tests/data/test100
cvs update: warning: `tests/data/test102' was lost
U tests/data/test102
cvs update: warning: `tests/data/test109' was lost
U tests/data/test109
cvs update: warning: `tests/data/test110' was lost
U tests/data/test110
cvs update: warning: `tests/data/test111' was lost
U tests/data/test111
cvs update: warning: `tests/data/test112' was lost
U tests/data/test112
cvs update: warning: `tests/data/test113' was lost
U tests/data/test113
cvs update: warning: `tests/data/test114' was lost
U tests/data/test114
cvs update: warning: `tests/data/test115' was lost
U tests/data/test115
cvs update: warning: `tests/data/test116' was lost
U tests/data/test116
cvs update: warning: `tests/data/test117' was lost
U tests/data/test117
cvs update: warning: `tests/data/test118' was lost
U tests/data/test118
cvs update: warning: `tests/data/test119' was lost
U tests/data/test119
cvs update: warning: `tests/data/test120' was lost
U tests/data/test120
cvs update: warning: `tests/data/test122' was lost
U tests/data/test122
cvs update: warning: `tests/data/test124' was lost
U tests/data/test124
cvs update: warning: `tests/data/test125' was lost
U tests/data/test125
cvs update: warning: `tests/data/test126' was lost
U tests/data/test126
cvs update: warning: `tests/data/test130' was lost
U tests/data/test130
cvs update: warning: `tests/data/test131' was lost
U tests/data/test131
cvs update: warning: `tests/data/test132' was lost
U tests/data/test132
cvs update: warning: `tests/data/test133' was lost
U tests/data/test133
cvs update: warning: `tests/data/test134' was lost
U tests/data/test134
cvs update: warning: `tests/data/test137' was lost
U tests/data/test137
cvs update: warning: `tests/data/test138' was lost
U tests/data/test138
cvs update: warning: `tests/data/test144' was lost
U tests/data/test144
cvs update: warning: `tests/data/test145' was lost
U tests/data/test145
cvs update: warning: `tests/data/test147' was lost
U tests/data/test147
cvs update: warning: `tests/data/test148' was lost
U tests/data/test148
cvs update: warning: `tests/data/test190' was lost
U tests/data/test190
cvs update: warning: `tests/data/test195' was lost
U tests/data/test195
cvs update: warning: `tests/data/test196' was lost
U tests/data/test196
cvs update: warning: `tests/data/test211' was lost
U tests/data/test211
cvs update: warning: `tests/data/test212' was lost
U tests/data/test212
cvs update: warning: `tests/data/test227' was lost
U tests/data/test227
cvs update: warning: `tests/data/test228' was lost
U tests/data/test228
cvs update: warning: `tests/data/test229' was lost
U tests/data/test229
cvs update: warning: `tests/data/test235' was lost
U tests/data/test235
cvs update: warning: `tests/data/test236' was lost
U tests/data/test236
cvs update: warning: `tests/data/test237' was lost
U tests/data/test237
cvs update: warning: `tests/data/test238' was lost
U tests/data/test238
cvs update: warning: `tests/data/test250' was lost
U tests/data/test250
cvs update: warning: `tests/data/test252' was lost
U tests/data/test252
cvs update: warning: `tests/data/test254' was lost
U tests/data/test254
cvs update: warning: `tests/data/test261' was lost
U tests/data/test261
cvs update: warning: `tests/data/test280' was lost
U tests/data/test280
cvs update: warning: `tests/data/test290' was lost
U tests/data/test290
cvs update: warning: `tests/data/test400' was lost
U tests/data/test400
cvs update: warning: `tests/data/test402' was lost
U tests/data/test402
cvs update: warning: `tests/data/test511' was lost
U tests/data/test511
cvs update: warning: `tests/data/test520' was lost
U tests/data/test520
cvs update: warning: `tests/data/test521' was lost
U tests/data/test521
cvs update: warning: `tests/data/test526' was lost
U tests/data/test526
cvs update: warning: `tests/data/test527' was lost
U tests/data/test527
cvs update: warning: `tests/data/test528' was lost
U tests/data/test528
cvs update: warning: `tests/data/test530' was lost
U tests/data/test530
cvs update: warning: `tests/data/test532' was lost
U tests/data/test532
cvs update: warning: `tests/data/test533' was lost
U tests/data/test533
cvs update: warning: `tests/data/test534' was lost
U tests/data/test534
cvs update: warning: `tests/data/test538' was lost
U tests/data/test538

although this was on Win32 with Tortoise CVS - I've seen same on Linux too...
last time when I had the problems with the tests I also did remove the whole curl dir, and checked out again which fixed the prob.

Guenter.
Received on 2007-04-21