Re: Committed: fd_truncate test-cases updated for recent libgfortran changes

2011-05-05 Thread Hans-Peter Nilsson
> Date: Thu, 5 May 2011 19:36:47 +0300 > From: Janne Blomqvist > On Thu, May 5, 2011 at 00:52, Hans-Peter Nilsson > wrote: > > This time, it happened in 173155:173168. > > > > Usually, there's also a brief question whether all changes were > > intended, or perhaps that some of the regressing tes

Re: Committed: fd_truncate test-cases updated for recent libgfortran changes

2011-05-05 Thread Mike Stump
On May 5, 2011, at 9:36 AM, Janne Blomqvist wrote: > The testsuite uses the process return value to determine > success, right? But which values exactly constitute success > vs. failure? 0 is success, and != 0 is failure.

Re: Committed: fd_truncate test-cases updated for recent libgfortran changes

2011-05-05 Thread Janne Blomqvist
On Thu, May 5, 2011 at 00:52, Hans-Peter Nilsson wrote: > Once or twice a year some regression results from changed I/O > in libgfortran, such that some existing test-case starts > calling libgfortran/io/unix.c:raw_truncate, which on > limited-I/O-bare-iron targets will emit "required ftruncate or

Committed: fd_truncate test-cases updated for recent libgfortran changes

2011-05-04 Thread Hans-Peter Nilsson
Once or twice a year some regression results from changed I/O in libgfortran, such that some existing test-case starts calling libgfortran/io/unix.c:raw_truncate, which on limited-I/O-bare-iron targets will emit "required ftruncate or chsize support not present" and fail. After a while, I get to i