Quantcast

Changes to status/Jamfile.v2

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Changes to status/Jamfile.v2

Belcourt, Kenneth
Hi,

Been gone for a while, noticed some changes to develop status/Jamfile.v2 that I don’t quite understand.  Can anyone tell me how to test just graph, graph_parallel, and mpi?  I used to be able to edit the status/Jamfile.v2 and remove all other libraries and leave just these three, then run ../b2 to test just these products.  That no longer works, hopefully there’s an easy way to accomplish this same thing?  I have a hefty backlog of unread email so I apologize if the answer’s in there somewhere, I did a quick scan and didn’t see anything obviously applicable.

— Noel

_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to status/Jamfile.v2

Rene Rivera-2
On Sun, Jun 19, 2016 at 3:22 PM, Belcourt, Kenneth <[hidden email]> wrote:
Hi,

Been gone for a while, noticed some changes to develop status/Jamfile.v2 that I don’t quite understand.  Can anyone tell me how to test just graph, graph_parallel, and mpi?  I used to be able to edit the status/Jamfile.v2 and remove all other libraries and leave just these three, then run ../b2 to test just these products.  That no longer works, hopefully there’s an easy way to accomplish this same thing?  I have a hefty backlog of unread email so I apologize if the answer’s in there somewhere, I did a quick scan and didn’t see anything obviously applicable.

That's always been, and still is,  possible with:

b2 --limit-tests=graph --limit-tests=graph_parallel --limit-tests=mpi



--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [EXTERNAL] Re: Changes to status/Jamfile.v2

Belcourt, Kenneth

On Jun 19, 2016, at 2:42 PM, Rene Rivera <[hidden email]> wrote:

On Sun, Jun 19, 2016 at 3:22 PM, Belcourt, Kenneth <[hidden email]> wrote:
Hi,

Been gone for a while, noticed some changes to develop status/Jamfile.v2 that I don’t quite understand.  Can anyone tell me how to test just graph, graph_parallel, and mpi?  I used to be able to edit the status/Jamfile.v2 and remove all other libraries and leave just these three, then run ../b2 to test just these products.  That no longer works, hopefully there’s an easy way to accomplish this same thing?  I have a hefty backlog of unread email so I apologize if the answer’s in there somewhere, I did a quick scan and didn’t see anything obviously applicable.

That's always been, and still is,  possible with:

b2 --limit-tests=graph --limit-tests=graph_parallel --limit-tests=mpi

Hmmm, that options doesn’t seem to do anything.  I get the same output whether I pass —limit-tests or not, though the total number of targets is different.

sanj2010-193-132:boost kbelco$ ./b2 
Performing configuration checks

    - 32-bit                   : no  (cached)
    - 64-bit                   : yes (cached)
    - arm                      : no  (cached)
    - mips1                    : no  (cached)
    - power                    : no  (cached)
    - sparc                    : no  (cached)
    - x86                      : yes (cached)

Building the Boost C++ Libraries.


    - symlinks supported       : yes (cached)
    - C++11 mutex              : yes (cached)
    - lockfree boost::atomic_flag : yes (cached)
    - has_icu builds           : no  (cached)
    - zlib                     : yes (cached)
    - bzip2                    : yes (cached)
    - iconv (libc)             : no  (cached)
    - iconv (separate)         : yes (cached)
    - icu                      : no  (cached)
    - icu (lib64)              : no  (cached)
    - pthread-supports-robust-mutexes : no  (cached)
    - compiler-supports-visibility : yes (cached)
    - compiler-supports-ssse3  : yes (cached)
    - compiler-supports-avx2   : no  (cached)
    - gcc visibility           : yes (cached)
    - long double support      : yes (cached)
    - zlib                     : yes (cached)
    - bzip2                    : yes (cached)

Component configuration:

    - atomic                   : building
    - chrono                   : building
    - container                : building
    - context                  : building
    - coroutine                : building
    - coroutine2               : building
    - date_time                : building
    - exception                : building
    - fiber                    : building
    - filesystem               : building
    - graph                    : building
    - graph_parallel           : building
    - iostreams                : building
    - locale                   : building
    - log                      : building
    - math                     : building
    - metaparse                : building
    - mpi                      : building
    - program_options          : building
    - python                   : building
    - random                   : building
    - regex                    : building
    - serialization            : building
    - signals                  : building
    - sync                     : building
    - system                   : building
    - test                     : building
    - thread                   : building
    - timer                    : building
    - type_erasure             : building
    - wave                     : building

...patience...
...patience...
...patience...
...patience...
...patience...
...patience...
...found 23447 targets...
...updating 1201 targets...

This seems to build every Boost product that has a library.  Can I just run the tests graph, graph_parallel, and mpi, and not build anything I don’t depend on?  I’m pretty sure that we don’t depend on wave, meta-parse, context, etc...

sanj2010-193-132:boost kbelco$ ./b2 --limit-tests=graph,graph_parallel,mpi
Performing configuration checks

    - 32-bit                   : no  (cached)
    - 64-bit                   : yes (cached)
    - arm                      : no  (cached)
    - mips1                    : no  (cached)
    - power                    : no  (cached)
    - sparc                    : no  (cached)
    - x86                      : yes (cached)

Building the Boost C++ Libraries.


    - symlinks supported       : yes
    - C++11 mutex              : yes
    - lockfree boost::atomic_flag : yes
    - has_icu builds           : no
    - zlib                     : yes
    - bzip2                    : yes
    - iconv (libc)             : no
    - iconv (separate)         : yes
    - icu                      : no
    - icu (lib64)              : no
    - pthread-supports-robust-mutexes : no
    - compiler-supports-visibility : yes
    - compiler-supports-ssse3  : yes
    - compiler-supports-avx2   : no
    - gcc visibility           : yes
    - long double support      : yes
    - zlib                     : yes
    - bzip2                    : yes

Component configuration:

    - atomic                   : building
    - chrono                   : building
    - container                : building
    - context                  : building
    - coroutine                : building
    - coroutine2               : building
    - date_time                : building
    - exception                : building
    - fiber                    : building
    - filesystem               : building
    - graph                    : building
    - graph_parallel           : building
    - iostreams                : building
    - locale                   : building
    - log                      : building
    - math                     : building
    - metaparse                : building
    - mpi                      : building
    - program_options          : building
    - python                   : building
    - random                   : building
    - regex                    : building
    - serialization            : building
    - signals                  : building
    - sync                     : building
    - system                   : building
    - test                     : building
    - thread                   : building
    - timer                    : building
    - type_erasure             : building
    - wave                     : building

...patience...
...patience...
...patience...
...patience...
...patience...
...found 22760 targets...
...updating 1252 targets...



_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [EXTERNAL] Re: Changes to status/Jamfile.v2

Rene Rivera-2
On Sun, Jun 19, 2016 at 3:52 PM, Belcourt, Kenneth <[hidden email]> wrote:

On Jun 19, 2016, at 2:42 PM, Rene Rivera <[hidden email]> wrote:

On Sun, Jun 19, 2016 at 3:22 PM, Belcourt, Kenneth <[hidden email]> wrote:
Hi,

Been gone for a while, noticed some changes to develop status/Jamfile.v2 that I don’t quite understand.  Can anyone tell me how to test just graph, graph_parallel, and mpi?  I used to be able to edit the status/Jamfile.v2 and remove all other libraries and leave just these three, then run ../b2 to test just these products.  That no longer works, hopefully there’s an easy way to accomplish this same thing?  I have a hefty backlog of unread email so I apologize if the answer’s in there somewhere, I did a quick scan and didn’t see anything obviously applicable.

That's always been, and still is,  possible with:

b2 --limit-tests=graph --limit-tests=graph_parallel --limit-tests=mpi

Hmmm, that options doesn’t seem to do anything.  I get the same output whether I pass —limit-tests or not, though the total number of targets is different.

Different number of target is something different ;-) 

sanj2010-193-132:boost kbelco$ ./b2 
...found 23447 targets...
...updating 1201 targets...

This seems to build every Boost product that has a library.  Can I just run the tests graph, graph_parallel, and mpi, and not build anything I don’t depend on?  I’m pretty sure that we don’t depend on wave, meta-parse, context, etc...

sanj2010-193-132:boost kbelco$ ./b2 --limit-tests=graph,graph_parallel,mpi 
...found 22760 targets...
...updating 1252 targets...

That b2 invocation is different than what I said. And would end up not filtering. If you wanted to specify it as a single option you could use a regex:

b2 "--limit-tests=graph|graph_parallel|mpi"

But I find listing the repeated options clearer.


--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Loading...