Hi Eur,
Welcome to the matrix... Please first read, carefully, the wiki page
dedicated to this script. I've also given you plenty of example in my recent
posts.
There are plenty of options, that's true, but there are here for good
reasons ! First of all, it's because it's quite highly configurable. you'd
think it's too much ? Well I'm more than glad that my JALLIB_PYTHON env var
was useful for you :)
Some comment (but read them *after* you read the wiki page)
jallib test [-u|-a|-d|-m other_matrix.yaml] [-f testing_matrix.yaml]
> [-s path/to/sample] [-p picname] [-n pic1,pic2,...]
> [-g template.tmpl [-o page.html] [-1] [-t template.tmpl]]
>
>
> too many options!
>
No, there are all useful.
> -e: erase samples which are declared in the matrix, but don't exist
> anymore on the filesystem/repository. Ex: when samples are
> renamed
> the matrix needs to be updated (-u) to include renamed
> samples,
> then it needs to be pruned (-e) to remove old samples.
>
>
> erase. That can't be good.
>
Very important to keep the matrix up-to-date.
> -a: add or update a test result. If the test does not exist, it's
> added to the matrix, else results will be updated.
> The format is target:test_file:[EMAIL PROTECTED]
> If pysvn module is installed, will automatically get revision
> information for given sample. Else, you'll need to specify the
> revision, using @revision format. Using the full format with
> revision will also bypass getting information from SVN using
> pysvn, even if this module is installed.
>
> For example:
> * to register a new test which passed, for 16f88
> -a 16f88:new_test.jal:true
> * to register a new test which failed, for 16f877
> -a 16f877:new_test.jal:false
> * to register a new test, not run yet, for 16f648a
> -a 16f648a:new_test.jal:null
> * to register a new test without pysvn installed (manual),
> assuming the test is working for revision 143
> -a 16f628:new_test.jal:[EMAIL PROTECTED]
>
>
> ????? I'm taking the blue pill here.
>
No, no ! This is what you should use !
> -d: delete/unregister test. The format is: target:test_file. Ex:
> To remove a test from 16f88 device:
> -d 16f88:bad_test.jal
>
>
> delete. Can't be good.
>
Again, can be useful.
> -m: merge another testing matrix with the main one specified with
> option -f. All test results found in this other matrix will
> replace those found in the main matrix. This option, with -n one,
> allows to work on a small subset of PICs, and then re-integrate
> the results in the main testing matrix.
>
>
> Merge the Matrix! Better leave that to the Architect.
>
:) Sure, you can leave it to the architect. The usage scenario is:
* testers can register tests
* but they don't have access to svn
* so they post their matrix
* and the Architect merge their results.
You've lost me here. I was under the impression that a test matrix would
> generate samples for a certain PIC from board files and test.jal files. Does
> it?
>
No, the test matrix does not do this itself, it just stores testing results.
But the jallib wrapper does this !
> If so, how?
>
$ jallib help sample
Still Work In Progress, still needs automation.
>
> What about the myriad of other options?
>
Just explore ! Though I can guide too to the matrix :)
Seb
--
Sébastien Lelong
http://www.sirloon.net
http://sirbot.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---
