From: Edward Diener (eldiener_at_[hidden])
Date: 2020-09-25 15:02:14
On 9/25/2020 4:15 AM, Andrey Semashev via Boost wrote:
> On 9/25/20 6:39 AM, Edward Diener via Boost wrote:
>> On 9/24/2020 7:31 PM, Gavin Lambert via Boost wrote:
>>> On 25/09/2020 03:49, Edward Diener wrote:
>>>> I understand that it is a free resource for Boost testing and that
>>>> they may not offer much in the way of virtual memory, as well as
>>>> having certain time limits when something is running. But nearly all
>>>> my tests for intensive functionality in Boost PP and VMD run fine to
>>>> completion on my local computer, using gcc, clang, and VC++ on
>>>> Windows or Linux, whereas in the CI testing with Appveyor and Travis
>>>> CI there are numerous "out of memory" and "process killed on
>>>> timeouts" errors which prevents successful CI tests results. So for
>>>> my purposes of CI testing these CI facilities are almost useless on
>>>> the whole to tell me whether some change is valid or not. That's
>>>> fine. I just will pay little attention to the overall result of the
>>>> CI tests, since they do not reflect real world results because of
>>>> the CI limitations.
>>> Perhaps you should disable those specific tests for CI builds, while
>>> keeping them for the normal test matrix?Â That would keep both useful.
>> How do I tell in my jamfile when CI testing is occurring in order to
>> disable the tests for CI builds.
> You can set special environment variables in the CI config file, which
> you then test in the Jamfile. For example:
Thanks ! I forgot about the os.environ functionality in Boost Build,
although I have probably used it myself numerous times <g>.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk