Horst Schirmeier ab9c0edf10 DatabaseCampaign: run jobs for known-outcome exps, too
Although we know that a known_outcome=1 pilot does not exhibit
behavior different from the golden run, the database schema does not
yet know what this behavior looks like (in terms of result-table
column values).  In order to be able to JOIN valid results for all
memory writes in the trace table (fspgroup maps them all onto *one*
pilot per variant), we need to run these experiments, too.

Additionally, don't join the fspgroup table; we only need this one for
result calculations afterwards.

Change-Id: Idcd2991274fede84526b1eee68a231774625d11a
2013-12-05 19:27:44 +01:00
2013-09-10 17:43:32 +02:00
2013-11-06 17:37:20 +01:00
2013-11-13 17:15:19 +01:00

This is an import of the old danceos svn repository.  The Fail* development
started with rev 187, but this git import only contains revisions 956 and newer
due to directory structure changes.

Imported from external gitsvn checkout.
http://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html
Description
No description provided
Readme 38 MiB
Languages
C++ 45%
C 36.8%
Python 8.2%
Shell 1.7%
Makefile 1.6%
Other 6.2%