Closed
Bug 594849
Opened 14 years ago
Closed 14 years ago
Need way to pick up on valgrind in testconfig.txt
Categories
(Tamarin Graveyard :: Build Config, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: treilly, Assigned: treilly)
References
Details
Attachments
(2 files)
637 bytes,
patch
|
edwsmith
:
review+
edwsmith
:
superreview+
|
Details | Diff | Splinter Review |
3.28 KB,
patch
|
brbaker
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•14 years ago
|
||
Assignee: nobody → treilly
Status: NEW → ASSIGNED
Attachment #473619 -
Flags: superreview?(edwsmith)
Attachment #473619 -
Flags: review?(brbaker)
Comment 2•14 years ago
|
||
Can you elaborate on the bug this is fixing?
Is it that runtests.py doesn't work right if you specify -E "valgrind avmplus ...", or that we need to know if it's valgrind to enable valgrind-specific test suppressions?
Assignee | ||
Comment 3•14 years ago
|
||
This is a complete patch that shows what I'm going for.
Attachment #473670 -
Flags: superreview?(edwsmith)
Attachment #473670 -
Flags: review?(brbaker)
Comment 4•14 years ago
|
||
Comment on attachment 473619 [details] [diff] [review]
tack on -valgrind to AVMPLUS_BIN_TYPE
do you want this to be a binary type or a feature?
need a space between if and (RUNNING_ON_VALGRIND)
The extra call to AvmLog will format weridly if any custom log function automatically adds newline. it shouldn't, but caution. a conditional
expression wouldn't take the chance:
(RUNNING_ON_VALGRIND ? "-valgrind" : "")
Attachment #473619 -
Flags: superreview?(edwsmith)
Attachment #473619 -
Flags: superreview+
Attachment #473619 -
Flags: review?(brbaker)
Attachment #473619 -
Flags: review+
Updated•14 years ago
|
Attachment #473670 -
Flags: superreview?(edwsmith)
Assignee | ||
Comment 5•14 years ago
|
||
(In reply to comment #4)
> do you want this to be a binary type or a feature?
It doesn't feel like a feature to me, I have --enable-valgrind to compile in the client requests get the OPT_CXXFLAGS right but haven't made it a full fledged feature. Also even if --enable-valgrind is on we only want to do these testconfig exclusion if we are in fact running on valgrind.
> The extra call to AvmLog will format weridly if any custom log function
> automatically adds newline. it shouldn't, but caution. a conditional
> expression wouldn't take the chance:
>
> (RUNNING_ON_VALGRIND ? "-valgrind" : "")
But that expression is a bunch of const strings being concated together at compile time, a runtime expression wouldn't work there.
Comment 6•14 years ago
|
||
Comment on attachment 473670 [details] [diff] [review]
VM changes w/ testconfig changes
I would probably tweak the testconfig to just be .*valgrind.* , that is assuming that these tests also need to be skipped on x64
Attachment #473670 -
Flags: review?(brbaker) → review+
Assignee | ||
Comment 7•14 years ago
|
||
I haven't run on mac-x64 or lnx yet, I don't want to relax the wild cards until I know I need to
Assignee | ||
Updated•14 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•