Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
aboutsummaryrefslogtreecommitdiffstats
path: root/testing
Commit message (Collapse)AuthorAgeFilesLines
* testing: fix finding tests on new cmake versionsChristian Tismer6 days1-4/+6
| | | | | | | | | | | | By chance, cmake was installed by homebrew without any restrictions, and so version 4.0.2 happened to be installed which does no longer use the option "--force-new-ctest-process". Changed the analysis to look for "/bin/ctest" instead. This should work for a long time. Task-number: PYSIDE-2221 Change-Id: Idc16063953ba82d4053cc60a7e0ef11b71b7b571 Pick-to: 6.9 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Remove unnecessary use of 'object' in class constructionremoteobjectsdevCristián Maureira-Fredes2024-12-184-4/+4
| | | | | | | | | | | Considering we are not compatible with Python 2 anymore, we can drop the 'object' explicit inheritance in the class declaration. Pick-to: 6.8 Change-Id: Iac3a95aa9721c3ff1a755f457c0936ca157a8470 Reviewed-by: Shyamnath Premnadh <Shyamnath.Premnadh@qt.io> Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* testrunner: Lower the fail criterion if runs < 5Friedemann Kleint2024-12-121-0/+3
| | | | | | | | Amends 3898c6e674907f2ee647626b2408c7b325ae9b82. Pick-to: 6.8 Change-Id: Icb17736f843ffcf8367434c6523f93c132558014 Reviewed-by: Christian Tismer <tismer@stackless.com>
* testrunner: Add command line for the number of re-runsFriedemann Kleint2024-12-111-3/+5
| | | | | | | | As a drive-by, fix command the line help (needs to be f-string). Pick-to: 6.8 Change-Id: I96b38c41bca303af313402a93e3d4c7a350de4df Reviewed-by: Christian Tismer <tismer@stackless.com>
* Raise Python version to 3.8Friedemann Kleint2024-12-031-20/+19
| | | | | | | | | | | | | | Fix some oversights of previous changes: - Bump limited API - Fix CMake files - Remove outdated version checks from Python code - Adapt some documentation Pick-to: 6.8 Task-number: PYSIDE-2943 Change-Id: Id8d9c4c6bb0629948de28beb3c4274991f84ff08 Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* Desktop Deployment: Fix final application nameShyamnath Premnadh2024-08-091-1/+3
| | | | | | | | | - Additionally, adapt wheel_tester.py Pick-to: 6.7 Fixes: PYSIDE-2806 Change-Id: If2c0d8f186142797f3280136298ed299643824f5 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Python-3.10: Allow the new syntax for Python 3.9Christian Tismer2024-06-208-0/+8
| | | | | | | | Add a future statement to all Python source files. Task-number: PYSIDE-2786 Change-Id: Icd6688c7795a9e16fdcaa829686d57792df27690 Reviewed-by: Adrian Herrmann <adrian.herrmann@qt.io>
* Deployment: add permission support and create macOS bundle applicationShyamnath Premnadh2024-03-111-1/+6
| | | | | | | | | | | | | | | | | | - Look at the ast of the python files of the application to identify the permissions used by the application. Once the permissions are identified, pass the necessary NS property list key to be added to the Info.plist file to Nuitka. - For macOS, when deploying create a macOS application bundle (.app) by default. This makes it align more with Apple recommendations and Qt deployment. - Fix tests. - Fix wheel_tester.py to consider .app for macOS. Task-number: PYSIDE-1612 Task-number: PYSIDE-2468 Change-Id: Ie225c9a92c845b432a8e7eaa791a8aeb86ecd988 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* build: update dependencies and processCristián Maureira-Fredes2024-01-231-5/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Even though some packages are 'safer' to update, we cannot rely on having the CI discovering it on random integrations. Pinning the remaining packages and ordering them a bit. The update of the 'build' package (to create wheels) required the replacement of 'build.pep517' by the new 'pyproject_hooks' module, and other modification to the wheel artifacts. The removed dependencies are currently placed at the tool level requirements.txt so it's not like they are not needed anymore. Test and CI scripts were adapted in order to rely on the 'dist' directory rather than the 'dist_new' one, removing the old step of creating the wheels with 'setup.py bdist_wheel'. The entry points (console scripts) that we used to have in the 'setup.py' were moved to the 'pyproject.toml' in order to advance towards not relying on the setup.py file. Flake8 issues were addressed in the different files that this patch modified. Change-Id: I83480c1920206e11fcb9a45264b6beaf6f8b686b Pick-to: 6.6 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* testing: Improve the Python version info to get better controlChristian Tismer2023-12-073-0/+34
| | | | | | | | | | | | | | | | | | The QML bug that was identified by "bug_825" revealed a Python error which is persistent in Python 3.8 and was fixed in Python 3.9.12 and Python 3.10.4 . It was not possible to write a work-around without re-implementing large areas of the Python type system. We interrogate the TestRunner to obtain the full Python version. Otherwise we would have to exclude Python 3.8 to 3.10 completely. Task-number: PYSIDE-2230 Change-Id: Ica53c2e7b44cbbf5ec8ca1430ab65e6743beeff8 Pick-to: 6.6 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* wheel_tester.py: Test pyside6-deployFriedemann Kleint2022-11-111-3/+62
| | | | | | | Change-Id: Ia82bc0f56c37f24fcdf6454b2b6106cad4ed92d7 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io> Reviewed-by: Adrian Herrmann <adrian.herrmann@qt.io>
* wheel_tester.py: Add Python directory to the PATHFriedemann Kleint2022-11-041-1/+6
| | | | | | | | | It appears to be missing, causing errors like nuitka not finding patchelf. Pick-to: 6.4 Change-Id: Ie6a5ad948805dd40f26867b35243f75e0b34459f Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* build: replace distutils.log by simple loggerCristián Maureira-Fredes2022-10-132-5/+5
| | | | | | | | | | Adding simple logger based on the logging module to replace the distutils.log one. Task-number: PYSIDE-2079 Change-Id: I2a4996a57be701552005b57d2b1a251b9fc44c41 Reviewed-by: Christian Tismer <tismer@stackless.com> Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* build: rename our rmtree to avoid shutil conflictCristián Maureira-Fredes2022-06-291-3/+3
| | | | | | | | | | | There is an implementation in the 'utils' module that implements a 'rmtree' function to handle removing readonly files from a directory. To avoid confusion with shutil.rmtree we rename it to 'remove_tree'. Pick-to: 6.2 6.3 Change-Id: I3548ea81f36c87ba51fd984fcf7b1cd4cafd54d6 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Use SPDX license identifiersLucie Gérard2022-05-278-304/+16
| | | | | | | | | | | Replace the current license disclaimer in files by a SPDX-License-Identifier. Files that have to be modified by hand are modified. License files are organized under LICENSES directory. Task-number: QTBUG-67283 Change-Id: I065150015bdb84a3096b5b39c061cf0a20ab637d Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* PyEnum: Implement Switchable Qt Enums Using Python EnumsChristian Tismer2022-05-221-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The mapping from Qt Enum to Python Enum was considered to be difficult. Actually, it is easier than thought. As a minimum invasive approach, this implementation changes very little in the first place. The generation process of enums stays almost unchanged, which simplifies handling of the generated code very much. At the end of each generated Enum, we call a special function that grabs the newly generated enum, reads all items and produces a Python class that replaces the enum in-place. We don't generate Python code, but the functional API to create the new enums. There are lots of more optimizations possible, but this concept solves the issue nice and quickly. A harder problem was the need to map all QFlag structures to enum.Flag structures from Python. This caused a sometimes hacky coding because both the old and the new version are supported. This will be totally cleaned up when we remove the old implementation. Pick-to: 6.3 Task-number: PYSIDE-1735 Change-Id: I66991312f2d7b137f110a4db30702b8f3bf518dd Reviewed-by: Christian Tismer <tismer@stackless.com>
* testing: Increase the timeout for debug buildsChristian Tismer2022-05-171-1/+1
| | | | | | | | | | | | | | | | Certain tests use more time when testing a build with debug Python. Some tests also do more work when debugging is enabled. This led to unclear stops in debug build tests, resulting in critical information missing from the test log. Changing the timeout from 10 to 20 minutes does no harm and solves the issue. Task-number: PYSIDE-1735 Change-Id: Icd30d36186d1559e3991c1f2e83d0179cffa2d6c Pick-to: 6.3 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* flake8: fix style issues on testingCristián Maureira-Fredes2022-04-028-23/+23
| | | | | Change-Id: I4e3e922ff95040999bc3bb1463c2e29783d5ee14 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* build: script to create wheelsCristián Maureira-Fredes2022-03-291-6/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This approach intends to avoid modifying the current structure we have in build_scripts, and can replace the call: python setup.py bdist_wheel mainly encouraged by PEP517, and the need of having incremental wheels, to replace the current single PySide6 one. The current configuration allows to create two new wheels: PySide6_Essentials, and PySide6_Addons that contain all the essential and addons Qt modules defined by the Qt Installer tool, with some modifications due to the dependencies of certain tools. Check the README files for more info. The known PySide6 wheel is also generated, but it's empty in favor of using the previous two wheels as requirements, installing them automatically, to avoid modifying the usage of 'pip install pyside6' The strategy is based on the current logic behing 'prepare_packages' that we have been using. Once the modules are built, instead of removing those directories currently in 'build/your_env/package', we rename them. Inside this new directory, one can have the 'shiboken6', 'shiboken6_generator', and 'PySide6' directories, with eveything already packed with the required wheel structure. The main difference is that instead of using the content of PySide6 to build one build, we select some files with the MANIFEST.in to create another wheel. The wheel tag drops the old assumption of needing: cp36.cp37.cp38.cp39.cp310-abi3 and only uses: cp36-abi3 Additionally, for Linux, we follow PEP600 to use the GLIBC version in the wheel name instead of manylinux1, manylinux2010, etc... For the current CI configuration, we know we are using 2.28, which is the minimum supported version for Qt6, so the wheel will look like: PySide6-6.3.0-cp36-abi3-manylinux_2_28_x86_64.whl The coin scripts were configured as well, to add the call of the new create_wheels.py script, and test them via wheel_tester.py Note: This script is not intended to be used as a general purpose wheel creation tool, and it's purely focused on the current Qt CI. There are many ad-hoc configurations used in different functions, like the structure of a Qt installation, the usage of 'a' on the environment for limited-api, etc. Task-number: PYSIDE-1115 Fixes: PYSIDE-692 Change-Id: Ic12e428b8b9b64bbe2facb1c520595ccd2384497 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* testing: update wheel_tester.py to no longer use qmakeChristian Tismer2022-03-211-53/+13
| | | | | | | | | | | This patch removes qmake as an installer tool and updates wheel_tester to use Ninja, only. [ChangeLog][PySide6] wheel_tester was upgraded to work completely with CMake and Ninja. Change-Id: Idbcd4f06614cf1f6b19b7eb1cafd9e873bc6edd3 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Fix scriptableapplication to build on macOS with framework Qt, amendChristian Tismer2022-03-211-6/+5
| | | | | | | | | | | | | | | | The original fix worked with qmake, but the cmake version has a bug. The setting for "qt_core_library_location_dir" was two levels too deep. This fixes the cmake build as-is. The next check-in removes qmake and uses Ninja. Amends {471b05f35a9c57d7fa910cf9f11c7f5fdfbf2a93} Task-number: PYSIDE-623 Change-Id: I288f2e9cd9479843718fa8b498ded51c9c6b140b Pick-to: 6.2 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Blacklist testmodifydocumentation for macOSFriedemann Kleint2022-03-141-2/+6
| | | | | | | | | | The test has been observed to fail on ARM. Add a processor tag to blacklisting that gices "i364" or "arm" on macOS. Pick-to: 6.2 Change-Id: I746c98a15160ab1cf9385986a9ecbef99d6a9f65 Reviewed-by: Christian Tismer <tismer@stackless.com>
* testing: Allow for repetition of blacklist sectionsChristian Tismer2022-03-131-3/+2
| | | | | | | | | | | | | | | | | | The testing framework was written with the rule that sections may not repeated - only the last entry would persist. When adding a whole row of PyPy entries, it turned out to be a drawback. It is nicer if sections can be repeated without interaction. [ChangeLog][shiboken6] In blacklist.txt now sections can be repeated. They will be combined as one section. Task-number: PYSIDE-535 Change-Id: I5e2ac435c7508b542306b470eca50411ee01606b Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* testing: fix a bug that prevents commenting entriesChristian Tismer2022-03-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | When trying to fix PyPy by blacklisting, it was not possible to blacklist one bug. After a while it was clear: The entry in question was already present in another, PyPy unrelated position. The PyPy entries are at the end of blacklist.txt, and so the old entry was replaced. This is a drawback of the system that could be discussed. The problem: As a workaround and to keep things reproducible, I added a comment to the old entry and repeated the entry in the PyPy section with a comment, too. The final problem after long analysis was that comments were no longer possible since 2021-01-05, by a wrong cosmetic change. (2de3a763fa18d5c30c2cff25057f1b81ceeed231) Change-Id: Ibb34a98f010294f03fae7e478c40e5c8742da689 Pick-to: 6.2 Task-number: PYSIDE-535 Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* Move from distutils to setuptoolsCristián Maureira-Fredes2021-11-261-1/+1
| | | | | | | | | | This is motivated by the deprecation of distutils, and removal in future versions https://github.com/pypa/packaging-problems/issues/127 Pick-to: 6.2 Change-Id: I16448b69f98df6dc1d9a904b69eb69ed5f1093f5 Reviewed-by: Christian Tismer <tismer@stackless.com>
* PyPySide: add it as a true new build targetChristian Tismer2021-10-281-3/+12
| | | | | | | | | | | | | | | | | | PyPy has now an appendix of its name and version at the end of the build path name. There are special settings needed in command.py to locate it in the folder structure. An extra check for PyPy has been added to the test script, because PyPy still has many errors. We use only one test run and extended timeouts until some crucial errors are gone. The blacklist file now understands pypy, pypy.7.3.6 etc. Task-number: PYSIDE-535 Change-Id: Ic2ab88bf35c5a18320733eb2552eca9e4315d04f Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* testing: use f-strings, fixChristian Tismer2021-07-281-5/+6
| | | | | | | | | | | | | f-string usage was wrong in command.py with triple-quotes. The effect was quite visible when inspection build logs. Also note: f-string expressions cannot contain back-slashes. Amends 8c1b6d88c19633a7373c052a2af3f584ad2114f7. Change-Id: I9f02c19d6993fa5b47bb07f361297fbe8c105749 Pick-to: 6.1 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* testing: code styling with blackCristián Maureira-Fredes2021-07-206-95/+153
| | | | | | | | | Addressing the long lines, and inconsistencies with double and single quotes. Pick-to: 6.1 Change-Id: I2d18116f0dd9215fa3cfe15482e606fc064f42da Reviewed-by: Christian Tismer <tismer@stackless.com>
* testing: fix flake8 warningsCristián Maureira-Fredes2021-07-124-6/+6
| | | | | | Pick-to: 6.1 Change-Id: I58d0ff45607b585beb008499728998d46e4679bb Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* testing: use f-stringsCristian Maureira-Fredes2021-07-125-88/+79
| | | | | | | | Pick-to: 6.1 Change-Id: I55a614b5cabe9b3dcc45de17e7a22c47ae0e643d Reviewed-by: Christian Tismer <tismer@stackless.com> Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
* PyPySide: Do some preliminary cleanups before the transitionChristian Tismer2021-06-291-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | The transition to the future PyPy support needs some cleanups, first. The goal is to get rid of all macros which handle type objects. This works in PySide on Python, but not with PyPy, which is emulating the whole interface. The shibokengenerator expression if (type->isWrapperType() || type->isEnum() || type->isFlags()) return QString::fromLatin1("*PepType_SGTP(%1)->converter").arg(cpythonTypeNameExt(type)); builds a very unfortunate union of the three possible macro type extensions that makes it impossible to do incremental changes. `PepType_SGTP` is therefore now completely gone. Finding this problem was a major showstopper. Furthermore, the usage of the __builtins__ dict object is not PyPy compatible and replaced by the builtins module. Task-number: PYSIDE-535 Change-Id: Ic32431b665aae43bb8c9735f69a54f7b3fae8b48 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* testing: enforce that .pyi files are always testedChristian Tismer2021-06-181-3/+14
| | | | | | | | | | | | | | | | | | | | | Being able to run .pyi files in Python 3 is always assumed possible. Since this test is disabled in local builds, we were relying on correct configuration of COIN, but that failed. To be safe, we now add a test to wheel_tester as well that unconditionally tests all .pyi with all features enabled. A special problem was a name clash in Qt3DAnimation.pyi which uses the name "property" :-) An import of QtMultimedia seems not to work, always. This happened in wheel_tester.py in CI, only. Task-number: PYSIDE-1599 Change-Id: Ib158e710cec72287fe4a71c01254727ea9b6dc54 Pick-to: 6.1 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* wheel_tester: Enable it again for Qt >= 6 with NuitkaChristian Tismer2021-04-071-16/+53
| | | | | | | | | | | | With the usage of nuitka, we have a working compiled test, again. Only the scriptableapplication fails, and only for CMake. This will be fixed in another check-in. The PyInstaller test remains in the code for being re-enabled. Task-number: PYSIDE-1523 Change-Id: Ic831fa5b110bbff4150a01cb8a7344ae050aae02 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* testing: solve flake8 warningsCristian Maureira-Fredes2021-01-057-55/+51
| | | | | | Pick-to: 6.0 Change-Id: I75f1a367c8a86ec586820bd4a45339773c15a70a Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* testing: Add a "ci" keyword equivalent to the one in QtFriedemann Kleint2020-12-031-0/+2
| | | | | | | COIN-only failures can then be tagged accordingly. Change-Id: Ib7f5abaea48eee5feee5b676ba80421c66ffb08e Reviewed-by: Christian Tismer <tismer@stackless.com>
* Blacklist failing tests for Qt 6Friedemann Kleint2020-11-191-1/+1
| | | | | | | | | Tested using Qt 6 beta 5. Task-number: PYSIDE-1339 Task-number: PYSIDE-904 Change-Id: I378770df929327aa8aa502751baac482702520d7 Reviewed-by: Christian Tismer <tismer@stackless.com>
* python3: remove all obsolete "from __future__" import statementsChristian Tismer2020-11-091-1/+0
| | | | | | | | | | | Note that not all future statements can be removed: PEP 563 for instance deals with from __future__ import annotations Task-number: PYSIDE-904 Change-Id: Ia387ec87f3c68ca64d13e8e80191eda900f58638 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* testrunner: Report the number of failed testsFriedemann Kleint2020-11-061-3/+7
| | | | | Change-Id: I0e5f73d7bf0bb404dc77d6d016a211e61c09da91 Reviewed-by: Christian Tismer <tismer@stackless.com>
* Rename PySide2 to PySide6Friedemann Kleint2020-11-022-4/+4
| | | | | | | | Adapt CMake files, build scripts, tests and examples. Task-number: PYSIDE-904 Change-Id: I845f7b006e9ad274fed5444ec4c1f9dbe176ff88 Reviewed-by: Christian Tismer <tismer@stackless.com>
* replace **locals by f-strings where possibleChristian Tismer2020-11-022-13/+12
| | | | | | | | | This change affects mostly only my own sources which were prepared for the migration to Python 3.6 . Task-number: PYSIDE-904 Change-Id: I0c2cd59f6f625f51f876099c33005ac70ca39db9 Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* Remove old pyside2-tools directoryCristian Maureira-Fredes2020-10-311-1/+1
| | | | | | | | | | | | The tools directory was brought back as sources/pyside-tools and currently only holds the pyside_tool.py script to create the entry points for rcc and uic. Since the submodule is not present anymore, we remove also the reference from the testing step. Change-Id: I0bfa4509d44c9bd2a3e5fbf4ddb7fff7a2750f4d Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* TestRunner: Fix syntax errorFriedemann Kleint2020-10-291-1/+1
| | | | | | | Amends b78e5bd771f0d5a81692bc95f76929b092edf2f6. Change-Id: Idecff944c27c9473cd565224547a206199af8a30 Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* testing: remove __future__ and Python2 referencesCristian Maureira-Fredes2020-10-288-28/+5
| | | | | | Change-Id: I80079d8a0956e3cc9b27ceb5b5ea2cfc6c9c9449 Reviewed-by: Christian Tismer <tismer@stackless.com> Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Rename shiboken2 to shiboken6Friedemann Kleint2020-10-282-4/+4
| | | | | | | | Adapt CMake files, build scripts, tests and examples. Task-number: PYSIDE-904 Change-Id: I4cb5ee4c8df539546014b08202a7b1e98ed3ff07 Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* wheel_tester.py: No longer use class OPTIONS from the build scriptsFriedemann Kleint2020-10-071-12/+9
| | | | | | | | | The semantics have changed, the OPTIONS dict is not fully populated at startup. Task-number: PYSIDE-807 Change-Id: Ic076f4ec8d624119d11e6ee266e2f6ccdb702b1e Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* Testing: Fix a quirk introduced by pruningChristian Tismer2020-07-161-1/+4
| | | | | | | | | | | The newly introduced history pruning has a timing problem on RHel 7.6. We disable pruning now when COIN is active. This makes anyway only sense for multiple builds on a developer machine but not in COIN. Change-Id: Ic4b4f2e42303e343d222b98655300509f83c7288 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* testing: Automate pruning of old history entriesChristian Tismer2020-07-141-1/+26
| | | | | | | | | | The always growing list of invalid directory entries in the history will get pruned to only keep the latest days entries. Change-Id: Ie104ca9874f985f0040950f650390798f45fc6d5 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* Improve wheel_tester script a bitChristian Tismer2020-03-201-5/+9
| | | | | | | | | | | Wheel_tester forces installation of "shiboken2_generator". This is not needed for compile_using_pyinstaller, but building modules with cmake. This was not clear. In effect, just the log messages were made a bit more verbose and a clarifying comment was added. Change-Id: I7d7d9ce1e9911461d087d685ab5c1cb66c94aa27 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* testrunner: Fix disrupted lines in the error logChristian Tismer2020-02-206-58/+139
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Windows inserts extra newlines into the error log when certain errors occur like "Exit code 0xc0000409\n***Exception:" and that newline caused the parser match to fail. Note that this is the normal stdout. CMake does not use stderr. It makes no sense to fix the pipe structure of the script. Instead, the only fix needed was recognition of line breaks in the error log. You can see this also in the failure listing The following tests FAILED: 1 - pysidetest_constructor_properties_test (Exit code 0xc0000409 ) The following improvements were done: - add an extra pass that checks for broken lines in the error log - add ad extra plausibility check or consecutive test numbers - improve the output, program structure and add some documentation When there should still an unforeseen bug occurs, it will be recognized by the plausi-check and the test repetitions are immediately cancelled. We could also fix the output not to contain the line breaks, but that breaks the principle of keeping the original output and needs discussion by the developers. Fixes: PYSIDE-1229 Change-Id: Ib71f3361e78eb59f3469da172c74c719e9f08706 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Replace OPTION_* by a dictionaryCristián Maureira-Fredes2019-12-031-4/+3
| | | | | | | | | | | | Currently we are importing * from the options.py file, which is a problem for the linters to discover if we are properly using the options of the file. Having a dictionary provides also a better way of access these options, and it is more clean than having one variable per each option. Change-Id: Ie70bd88665357b85e2842c5df269857504ecccdf Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
generated by cgit v1.2.3 (git 2.25.1) at 2025-05-28 20:09:11 +0000