Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

write client for submitting results #6

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 7 comments
Open

write client for submitting results #6

GoogleCodeExporter opened this issue Mar 14, 2015 · 7 comments

Comments

@GoogleCodeExporter
Copy link

should be in perl

Original issue reported on code.google.com by [email protected] on 28 Aug 2007 at 5:36

@GoogleCodeExporter
Copy link
Author

The reporter expects to get things posted to '/results' or '/results.xml'

Report objects have the following attributes (from 001_create_results.rb)
pws,          :string # milestone for cws; null for milestone
cws,          :string # actually could be milestone
builder,      :string
host,         :string
build_number, :integer
data_type,    :string
data,         :text

Most of these are straightforward.  Data is a serialized hash.  In the 
database, it's
YAML encoded.  When sent in the xml, I have no idea.  I'm the
deserialization-reserialization works.  

From the console, Result.find(:first).to_xml yeilds:
<?xml version="1.0" encoding="UTF-8"?>
<result>
  <build-number type="integer">0</build-number>
  <builder>builder_2</builder>
  <created-at type="datetime">1969-12-31T16:00:00-08:00</created-at>
  <cws>SRC680_m0</cws>
  <data>megabytes1075</data>
  <data-type>tree_size</data-type>
  <host>host_2</host>
  <id type="integer">0</id>
  <pws>nil</pws>
</result>

This gives an overview of how it expects the XML to be formated.  One can see 
that
the data attribute is not serialized properly (the hash is { 'megabytes' => 
1075 }) 
Since the to_xml method is not required, this may not indicate a problem.  
However,
how it expects data to be serialized is still a mystery.  I would try YAML 
first. 
Note that created_at need not be supplied, as the app will populate that 
attribute.

Original comment by [email protected] on 28 Aug 2007 at 9:29

@GoogleCodeExporter
Copy link
Author

Notes from IRC conversation:

The usage of pws/cws is unclear.  The purpose is for the ability to compare a 
cws to
it's milestone or milestones of the same master to be compared to each other. 
However, the usage detailed in 001_create_results.rb may need some reforming.  

The purpose of data_type is to indicate what sort of "result" this is.  To make 
this
more concrete, assume that we have the following "tests" that are run:
 1) measures tree size
 2) measures cold-start-time
 3) collects results of profiling startup

The datatype distinguishes between these types of data.  So, we could have 
data_type be:
 1) tree_size
 2) cold_start_time
 3) oprofile

The data is the serialized hash that represents the data in question.  For the 
above
examples, it could be (unserialzed):
 1) { 'megabytes' => 1024 }
 2) { 'seconds' => 12 }
 3) { 'symbols' => ['symbol_0', 'symbol_1', ... 'symbol_n'],
      'percent' => ['percent_0', 'percent_1', ... 'percent_n']}

Original comment by [email protected] on 28 Aug 2007 at 10:00

@GoogleCodeExporter
Copy link
Author

The deprecating of result and move to data_items and data changes this, but only
slightly.  I would recommend the implementer use Perl and XMLSimple to get the 
job done.

Original comment by [email protected] on 30 Aug 2007 at 12:08

@GoogleCodeExporter
Copy link
Author

For the rails newbies in the audience, one starts the application with 
script/server

You then have a web server on port 3000 of localhost and can start testing.  
logs are
in log/development.log


Original comment by [email protected] on 30 Aug 2007 at 12:11

@GoogleCodeExporter
Copy link
Author

adding milestone, component

Original comment by [email protected] on 2 Sep 2007 at 4:31

  • Added labels: Component-Slave, Milestone-DataGathering

@GoogleCodeExporter
Copy link
Author

starting

Original comment by [email protected] on 5 Sep 2007 at 12:36

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 13 Aug 2008 at 2:33

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant