Re: BETA: ci-scripts 3.0 (feat. Windows on Travis)

[Ralph Lange via Core-talk <core-talk at aps.anl.gov>]

Hi Mark,

On Wed, 10 Jun 2020 at 22:09, Mark Rivers <rivers at cars.uchicago.edu> wrote:

 

Mea culpa, I should have looked at the README.md more carefully. ADD_MODULES was exactly what I was looking for.

 

I will make that clearer.

 Actually I think the README only documents omitting the .set in the context of the “include” statement, not the SET statement.  There is one example (SET=stable) that omits the .set.

Another thing that I will clarify in the doc.

 

 Ø  Also: the 'STATIC=YES/NO' setting has been replaced by 'BCFG=default/static/debug/static-debug'.

 Yes, I had made all of those changes already.

Well, job 19 still has "STATIC=YES" and job 21 has "BCFG=statuc", both of which will not cause the build to be linking statically.

I will make the script check more carefully and complain loudly.

What –j count is being used by that job?  Is see that cue.py has these lines:

 

cue.py:    parallel = kws.pop('parallel', 2)

cue.py:        makeargs = ['-j{0}'.format(parallel)]

 

I suspect that means there is a default value of –j2.  How does one specify a different value for “parallel”?

Not available through the API. I can add that.

The parallel value is supposed to be set per service, but all VMs that Travis and AppVeyor offer have 2 cores, so hard coded for the moment.

Thanks a lot for your feedback!

Cheers,
~Ralph