Open main menu

CDOT Wiki β

Changes

SPO600 Framework Project

936 bytes added, 20:15, 23 October 2015
Instructions for Submitting a Pull Request
== API Specifications ==
''' config file''' -> name of package write to file (analys.txt) for benchmark<br>config file-> ''' parse config ''' -> one group per line, options delimited by "|" (STDOUT)<br> ''' permute options ''' -> one permutation per line (STDOUT) + ID of groups and group itself to analys.txt<br> ''' build ''' -> status code and location of start up script + build time, memory used, load of CPU (or it can be called in main) and status code to analys.txt<br> ''' test ''' -> status code + status code to analys.txt
analys.txt ->''' benchmark ''' -> SQL Database
Basically, ''' analys.txt ''' would look like this:
Replace items in angle braces with your values<pck br />// denotes a comment<pre><package name - file nameof the archive> ID1 of group of options + #<permutation number, starting with 1>|<compiler options> // # symbol delimits a complete result set ID1 <build exit code>|<build wall clock time>|<build user + system time>|<binary size in bytes> // from build step - time, memory, CPU load, status code of buildis in seconds ID1 + status <test exit code of > // from teststep ID2 +options ID2 + build time$<benchmark run number, start with 1>|<benchmark speed performance score>|<benchmark memoryscore> // from benchmark step, CPUboth are integers >= 0, status code of buildhigher is better etc// repeat above line for each benchmark run<pck name 2/pre> ID1 etc
Example:
<pre>ID can be used just once apache2.2.31.tgz // package name#1|-fbuiltin -falign-loops -fforward-propagade -fipa- in this case it can be like a delimiter tat separates groups of cp // options0|30|90|1024 // build0 // test$1|1334|4532 // benchmark run 1$2|1543|54354 // benchmark run 2$3|4543|44$4|1543|4565#2|-O3 // permutation 20|20|60|2048 // etc.0This is just a draft.$1|13434|45532$2|56643|5436654$3|45433|4674$4|154563|455465</pre>
== GitHub Repository ==
# Click the Fork button.
# This should create a your own version of the repo.
# Clone the newly forked repo , by copying the "HTTPS Clone URL" on the right side of the repo page, and running the command "git clone https://github.com/pk400/SPO600-Build-Framework.git" in your Git Shell and begin adding your additions/changes.
# Once you have committed and pushed your changes to your own repo, submit a Pull Request, by clicking on the link on the right side of the repo page.
# Click New Pull Request.
1
edit