I would try this manually, without the php script in between.
1. I would modify the .php script to write out a file
2. send a submit through the .php file
3. examine the resulting file and ensure that all the fields match up to
what you think they should be
4. manually submit this file to perfbase and see what happens
That's what I would do.
> -----Original Message-----
> From: mtt-users-bounces_at_[hidden]
> [mailto:mtt-users-bounces_at_[hidden]] On Behalf Of Ethan Mallove
> Sent: Tuesday, July 18, 2006 6:33 PM
> To: mtt-users_at_[hidden]
> Subject: [MTT users] perfbase.php not slurping test run data
> perfbase.php seems to only populate perfbase with mpi_install
> and test_build
> data. In other words, data correlating to these files is
> getting input to
> Data correlating to this file is _not_ getting input to perfbase:
> I verified this by looking at the perfbase data with pg_dump
> command-line tool to dump the entire database), which shows
> that there is no
> data for these fields:
> The above fields belong to the rundata table. I can see from
> the perfbase
> --debug output there are UPDATEs/INSERTs into the below tables, but no
> UPDATEs/INSERTs into rundata:
> It looks like the data is getting parsed correctly:
> #* checking <named_location>: found 'test_name: '
> #* parsing <named_location> 'test_name: '
> content for 'test_name': 'f77_hello'
> *# Processing line:
> test_np: 2
> #* checking <named_location>: found 'test_np: '
> #* parsing <named_location> 'test_np: '
> content for 'test_np': '2'
> ... [snip] ...
> And there are no error messages from perfbase. Can anyone
> give me a tip on how
> to track down the missing data?
> mtt-users mailing list