[RTEMS Project] #2375: tftpDriver free's current_directory

[RTEMS trac]

#2375: tftpDriver free's current_directory
-------------------------+---------------------
 Reporter:  mdavidsaver  |       Owner:
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:  4.10.3
Component:  networking   |     Version:  4.10
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by gedare):

 Replying to [comment:4 mdavidsaver]:
 > Replying to [comment:3 gedare]:
 > > ... Pulling in all the changes since 4.11 includes many extraneous
 modifications.
 >
 > Agreed, though I think most of the extraneous changes are reverted in
 the 2nd revision.
 >
 > > Is there an EPICS maintainer who might be able to comment?
 >
 > On?
 >
 The value of this fix.

 > > Can you pull out the close() false error and put it into a separate
 ticket?
 >
 > #2376
 >
 Thanks

 > > It might be nice to put the rtems-tftp-test into the testsuite with
 some reformatting to fit the test patterns. (Might make a suitable set of
 Google Code-In tasks if we have that this year.)
 >
 > Suggestions on how to structure this would be welcome.  I wasn't sure
 how to do this since the test depends on files being present on the tftp
 server (and on a BSP with support for networking).

 Ah, yes good point, actually running this test is problematic for most
 targets. The way we get around that in 4.11+ is to add the test to the
 list of exempted tests in a file in each BSP that gets read by the
 automated test runner. Thus, if a test only works on one BSP, it would be
 black-listed on all the other BSPs. This test would have additional
 constraints though (networking, connected server) that make it harder to
 fit in the current testing framework.

 For now, it might be best to put the test into the network-demos
 repository. The existing Makefile should just about work there, and
 someone can do the 'waf' part easily enough.

--
Ticket URL: <http://devel.rtems.org/ticket/2375#comment:5>
RTEMS Project <http://www.rtems.org/>
RTEMS Project