dolfin team mailing list archive

[Harish Narayanan <harish.mlists@xxxxxxxxx>]

On 8/26/10 6:28 PM, Johannes Ring wrote:
> On Wed, Aug 25, 2010 at 5:25 PM, Anders Logg <logg@xxxxxxxxx> wrote:
>> On Wed, Aug 25, 2010 at 08:52:57PM +0530, Harish Narayanan wrote:
>>> On 8/25/10 6:41 PM, Johannes Ring wrote:
>>>> What are the steps that the buildbot should run for building and
>>>> testing DOLFIN with CMake? I have currently simply converted the steps
>>>> that was used before with the SCons based build system. It is
>>>> basically running the following steps:
>>>>
>>>> * Update
>>>> * Clean up from last build
>>>> * Disable all optional packages and run make
>>>> * Enable demos and run make
>>>> * Enable UFMPACK, CHOLMOD, MTL4, CGAL, Python, and zlib and run make
>>>> * Enable MPI, SCOTCH, ParMETIS, and Trilinos and run make
>>>> * Enable PETSc, SLEPc, and GMP and run make
>>>> * Set install prefix and run make install
>>>> * Enable benchmarks and run make
>>>> * Enable tests and run make
>>>> * Run tests
>>>>
>>>> Some of these steps doesn't do anything with the new build system
>>>> (demos, benchmarks, and tests doesn't get built). Any suggestions for
>>>> what the steps should be?
>>>
>>> Would it be possible to move the buildbots to dorsal too? That
>>> automatically adds another level of tests for the build script.
>>>
>>> Harish
>>
>> I've been thinking of that too.
> 
> I could try to add Dorsal to the buildbot. In that case, what steps
> should the buildbot run? What should be cleaned up between each run?
> Only installed files or downloaded and build files aswell? What tests
> should be run? I guess the DOLFIN tests?

Has there been any progress on this front?

Harish