summaryrefslogtreecommitdiff
path: root/status
Commit message (Collapse)AuthorAgeFilesLines
* Update explicit-failures-markup.xmlAutomated Commit2017-10-261-40/+40
|
* Update explicit-failures-markup.xmlAutomated Commit2017-10-261-0/+1
|
* simplified poly_collection toolset specification (#169)joaquintides2017-10-211-30/+21
|
* updated according to current toolset naming conventions (#168)joaquintides2017-10-211-21/+21
|
* Update explicit-failures-markup.xmlAutomated Commit2017-10-201-4/+7
|
* Update explicit-failures-markup.xmlAutomated Commit2017-10-191-30/+12
|
* Update explicit-failures-markup.xmlAutomated Commit2017-10-131-5/+45
|
* Update explicit-failures-markup.xmlAutomated Commit2017-10-111-0/+13
|
* Update explicit-failures-markup.xmlAutomated Commit2017-10-101-3/+6
|
* Merge pull request #165 from boostorg/danieljames-patch-3Daniel James2017-10-091-3/+3
|\ | | | | Make all elements in explicit failures schema optional
| * Make all elements optionaldanieljames-patch-3Daniel James2017-10-031-3/+3
| | | | | | This is so that this schema can be used to validate module markup (such as https://github.com/boostorg/functional/blob/develop/meta/explicit-failures-markup.xml). An alternative solution would be to have a separate schema file for submodules, espcially if the reporting scripts require these elements to be present.
* | Merge pull request #164 from boostorg/danieljames-patch-2Daniel James2017-10-091-1/+1
|\ \ | | | | | | Remove --valid flag from xmllint
| * | Remove --valid flag from xmllintdanieljames-patch-2Daniel James2017-10-031-1/+1
| |/ | | | | | | | | | | | | | | The existing call to xmllint returns an error status, the error message is obscured by the output, but it writes to stderr: explicit-failures-markup.xml:3: validity error : Validation failed: no DTD found ! xsi:noNamespaceSchemaLocation="explicit-failures.xsd"> According to the xmllint man page the `--valid` flag is used for validating using a DTD, and we don't have a DTD. The `--schema` flag is sufficient for validation, so I think the solution is just to remove the `--valid` flag.
* | Update explicit-failures-markup.xmlAutomated Commit2017-10-071-10/+53
| |
* | Use mark-unusable for contractDaniel James2017-10-051-3/+2
|/
* Update explicit-failures-markup.xmlAutomated Commit2017-10-021-1/+11
|
* Add contract failure markupDaniel James2017-09-291-0/+23
|
* Add quick, minimal targets to status/JamfilePeter Dimov2017-09-041-0/+26
|
* Add --no-check-libs option to `b2 status`Peter Dimov2017-09-041-1/+5
|
* Merge pull request #154 from vinniefalco/developDaniel James2017-07-301-0/+42
|\ | | | | Update explicit-failures-markup.xml for beast
| * Update explicit-failures-markup.xml for beastVinnie Falco2017-07-291-0/+42
| |
* | enabled GCC 4.8+ for poly_collectionjoaquintides2017-07-291-5/+26
|/
* Merge pull request #126 from olk/patch-21Daniel James2017-06-231-0/+29
|\ | | | | list of excludedd compilers for boost.fiber
| * list of excludedd compilers for boost.fiberOliver Kowalke2016-06-081-0/+29
| |
* | added qcc unusable toolsets to poly_collectionjoaquintides2017-06-231-0/+2
| |
* | marked unusable toolsets for poly_collectionjoaquintides2017-06-181-0/+27
| |
* | Less greedy about declaring tests.Rene Rivera2017-05-291-4/+4
| | | | | | Only declared tests that are filtered in for actual testing.
* | Don't use non-existent test projects.Rene Rivera2017-05-261-1/+4
| |
* | Add Boost.Geometry test category.Adam Wulkiewicz2016-08-281-0/+2
| |
* | Add ability to exclude tests with options. And make the filtering as toRene Rivera2016-08-111-10/+70
| | | | | | | | which tests to run from status dir composable. This hopefully goes a long way towards easier control of running limited set of tests.
* | Require that the library check targets use to host OS as the target OS.Rene Rivera2016-07-161-0/+6
| | | | | | | | This has the effect of only using the host OS python interpreter when running the tests.
* | Add support for parent lib meta data to include sublib meta data.Rene Rivera2016-07-071-3/+48
| |
* | Remove some more special cases.Daniel James2016-07-031-3/+0
| |
* | Remove custom libraries from test list that are now automaticallyRene Rivera2016-06-281-21/+0
| | | | | | | | | | handled by sublibs trigger file. Also remove etraneous example and other extra test targets, authors will need to add them into their libs if truly needed.
* | Add support for "sublibs" trigger file for automatic testing ofRene Rivera2016-06-281-16/+22
| | | | | | sub-libraries.
* | Run 'hash' tests using more traditional location.Daniel James2016-06-261-1/+1
| | | | | | Will update the library soon.
* | Remove special cases for 'unordered' tests.Daniel James2016-06-261-2/+0
| | | | | | They're not actually required, it runs just fine from `libs/unordered/tests`.
* | Add debug option for library checking to get some output of what pathsRene Rivera2016-06-171-30/+52
| | | | | | | | the script checks. Also add keys for each check to eventually use for filtering.
* | Fix header check error that was supposed to be a warning.Rene Rivera2016-06-151-2/+2
| |
* | Merge pull request #128 from jzmaddock/patch-12Rene Rivera2016-06-141-1/+0
|\ \ | | | | | | Remove reference to static_assert Jamfile no longer needed.
| * | Remove reference to static_assert Jamfile no longer needed.jzmaddock2016-06-141-1/+0
| | |
* | | Remove unnecessary reference to regex examples.jzmaddock2016-06-141-1/+0
|/ /
* | Remove debug-commented code.Rene Rivera2016-06-121-0/+6
| |
* | Put back use-project in case of non-filtered lib.Rene Rivera2016-06-121-1/+1
| |
* | Automate core way of testing libraries (i.e. root/lib/test requirement)Rene Rivera2016-06-101-114/+14
| | | | | | for most current tests.
* | Merge branch 'develop' of https://github.com/boostorg/boost into developRene Rivera2016-06-091-0/+1
|\ \ | |/
| * add fiber to regression testsOliver Kowalke2016-06-071-0/+1
| |
* | Add testing to check initial set of library requirements.Rene Rivera2016-06-092-5/+273
|/
* Add qvm to status/Jamfile.v2Peter Dimov2016-04-051-0/+1
|
* Merge pull request #111 from ldionne/developDaniel James2016-01-241-0/+19
|\ | | | | [status] Add expected test failures for Hana
View Lorry Controller Status