public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Mats Liljegren <mats.liljegren@enea.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] ltplite test case crashes
Date: Mon, 14 Apr 2014 12:17:21 +0200	[thread overview]
Message-ID: <20140414101720.GB24840@rei.suse.cz> (raw)
In-Reply-To: <20140411105953.02bcf46e@mats-desktop>

Hi!
> This is most likely the case, since all files, including root file
> system, are in RAM. ;-)
> 
> I tried to use "-d <path>" and also used same <path> as current working
> directory in order to force file creations there, but I got the same
> error. Is "-d" the option to use to solve problems like this? Or are
> there other techniques?

I've looked at the source code and the TMPDIR is not passed to growfiles
in the runtest file nor is TMPDIR utilized in the growfiles sources so
as far as I can see it seems defaults to current directory which should
be /opt/ltp/....

I would call this a bug.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      parent reply	other threads:[~2014-04-14 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 16:03 [LTP] ltplite test case crashes Mats Liljegren
2014-04-10 16:32 ` chrubis
     [not found]   ` <20140411105953.02bcf46e@mats-desktop>
2014-04-14 10:17     ` chrubis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140414101720.GB24840@rei.suse.cz \
    --to=chrubis@suse.cz \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=mats.liljegren@enea.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox