aboutsummaryrefslogtreecommitdiffstats
path: root/build_history/blacklist.txt
Commit message (Collapse)AuthorAgeFilesLines
* testing: Improve the Python version info to get better controlChristian Tismer2023-12-071-2/+18
| | | | | | | | | | | | | | | | | | 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>
* Shiboken: Fix subtle bug caused by PyPy support and "bug_825"Christian Tismer2023-11-141-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When implementing PyPy support, all Shiboken types lost their hidden extra fields, because they were replaced by shadow dicts. This creates a problem with multiple inheritance. In Python < 3.12, the decision which base type will create the instance is driven simply by the size of the type. In class MetaC(MetaA, MetaB): pass when MetaA is derived from type and MetaB is derived from SbkObjectType, MetaA is not the type that should win. Fixed by simply adding 1 to the default size of PyType_Type. Caused by bug_825 corrected version. The old test is retained as bug_825_old.py . NOTE: This touches a Python 3.8 bug that was fixed in 3.9.12 and 3.10.4 - unfortunately CI Python is older in all cases. Task-number: PYSIDE-2230 Change-Id: I6e82cafb83c8351bbbeafcc80e11d5e45568f73d Pick-to: 6.2 6.5 6.6 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
* Implement custom asyncio event loop based on QtAdrian Herrmann2023-07-271-0/+2
| | | | | | | | | | | | asyncio is an established library for Python applications with concurrency and asynchronous I/O, and the de facto standard that multiple other async frameworks build upon. Like Qt, it is based on an event loop, so to this end, it offers an extensive API to implement custom event loops that applications using asyncio can then leverage. Task-number: PYSIDE-769 Change-Id: I3daf5d631e2fa0d44fd8c3c272ac5cce96f58653 Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* PySide6/SignalManager: Fix memory leaks connecting free methods/lambdasFriedemann Kleint2023-06-281-4/+0
| | | | | | | | | | | | | | | | | Change 1270a9e82e5bc3bd53a1131698ece60403da1192 changed the deletion of global receivers from listening to QObject::destroyed() (which caused thread issues) to using QPointer<> and purging the lists in notify. What is missing was the deletion of global receivers that are not tied by weak reference to a Python instance. Add a check in notify() to clean out the empty global receivers. Pick-to: 6.5 Fixes: PYSIDE-2371 Fixes: PYSIDE-2299 Task-number: PYSIDE-2141 Change-Id: I39dca2a21088930c9a7f8e5eb7e948b3fff49b4b Reviewed-by: Christian Tismer <tismer@stackless.com> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
* Revert anonymous slot memory leak fixAdrian Herrmann2023-06-021-0/+4
| | | | | | | | | | | | | | | The fix to PYSIDE-2299 unfortunately introduces regressions that are more serious than the memory leak caused by an edge case that was originally supposed to be fixed. A different approach will be needed to fix the memory leak, in the meantime, revert the change. The corresponding unit test remains blacklisted, as it will apply to a future fix. Pick-to: 6.5 Fixes: PYSIDE-2346 Task-number: PYSIDE-2299 Change-Id: I1dcddb03f731a333f6acf7c9df79b9dba42bec21 Reviewed-by: Christian Tismer <tismer@stackless.com>
* property: fix an old refcount bug, concluding debug errorsChristian Tismer2023-02-201-3/+0
| | | | | | | | | | | | | | | | There was a refcounting bug in pysideproperty.cpp that took some time to be understood. By using Property.__init__ multiple times, an omission became manifest: Not clearing a Property instance's attribute before generates a leak. This was the last unsolved reference bug in debug mode :-) Change-Id: Ie91fa9e56ef52ca555168841c99c14fd550202ed Fixes: PYSIDE-1402 Pick-to: 6.4 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Blacklist qmultimediawidgets on macOS/COINFriedemann Kleint2023-02-131-0/+3
| | | | | | | | | | The COIN machine cannot create a Metal surface. Pick-to: 6.4 Change-Id: I68a32496c42b903a210f297fe7248717c8ed60ca Reviewed-by: Adrian Herrmann <adrian.herrmann@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Christian Tismer <tismer@stackless.com>
* Adapt to Qt 6.5Friedemann Kleint2023-02-091-1/+0
| | | | | | | | | | | | | | | | | | | | - Add new enums - Hide field QMetaMethod::mobj made protected by qtbase/0b701ec0cd86afbf6bb0d0abb361cfb6500c2e1b - Adapt to PDF qtwebengine/6769bd1544c56a514fe35bf16d05614605a49bea - Adapt to qhttpserver/55d10201dc7a47b239825548e053c1fb0de61115, adding a virtual method with rvalue reference to QAbstractHttpServer - create_wheels.py: Adapt to changed location of the metatypes directory in Qt after qtbase/4234ce12dc819b9ca76c8dc4c251f5bd4fe0bc9c. - Adapt error column in QDomDocument test - Fix QMetaObject::invoke() to work after qtbase/fe92b080658f0d8609e2a2a69e5ec2b51dd7bf9d by making the cast of the helper types to Q(Generic)ReturnArgument explicit in the snippets Change-Id: Ifb514878e999ad4c9ef00ff83172626eff112a3d Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Shyamnath Premnadh <Shyamnath.Premnadh@qt.io>
* signal: Finally clean up all leaks after complete understandingChristian Tismer2023-02-071-2/+0
| | | | | | | | | | | | | | | | | | | | | The PYSIDE-79 bug was never understood, completely. After getting much more clarity through the work on PYSIDE-2201, the real problem could be found: It turned out that the implementation of descriptors was incomplete. Instead of respecting an already cached instance, it created a new one, all the time, resulting in a serious leak! This became visible by deep inspection of the control flow with VS-Code. After the interaction of PyObject_GetAttr, getHiddenDataFromQObject and signalDescrGet became transparent, the function was completed and the issue finally solved. Fixes: PYSIDE-79 Task-number: PYSIDE-68 Task-number: PYSIDE-2201 Change-Id: Ifd6098b1ce43d9bf51350218deb031bbf9ccb97a Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* signature: Update, cleanup and install signature testChristian Tismer2022-08-171-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | The signature tests were disabled for a long time. Meanwhile, a number of unresolved values have piled up. The reason was partially a weird mixture of intents that made it unpractical to run the full tests on every platform. Mamely, macOS was quite unclear about which signatures have to exist and which don't. This overhaul does the following: * The various Shiboken modules were removed from the tested signatures * A pure test is added that only checks for no offending lines As effect, signatures are tested unconditionally without any other conditions. The other tests remain disabled. Task-number: PYSIDE-510 Change-Id: Id9e65ed7324a795966f460e13dd95fd5cebcca6a Pick-to: 6.3 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Blacklist smartpointer tests on macOSFriedemann Kleint2022-06-071-0/+2
| | | | | | | | | | d1868d70f0f5ae38efd532911c5a7e28ebd02752 was not sufficient to fix the test. Pick-to: 6.3 Task-number: PYSIDE-454 Change-Id: Ibccf06af15df5150cab250ccbf516e0a9ab4dabf Reviewed-by: Christian Tismer <tismer@stackless.com>
* PyEnum: Prepare Enum tests for both old and new enums, amendedChristian Tismer2022-05-241-2/+0
| | | | | | | | | | | bug_462.py had a precedence bug that was fixed in 6.3, already. e must fix it here because the check-in was done already. Explicitly no pick-to. Task-number: PYSIDE-1735 Change-Id: Iaebd53e566bdfd73d2761268b3691f35c2f9de7c Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* PyEnum: Prepare Enum tests for both old and new enumsChristian Tismer2022-05-221-0/+2
| | | | | | | | | | | | | | | | | | These tests are now completely identical to the old tests and have an adapted Python Enum version if suitable. Both versions can be selected once at runtime. Having both test versions available as a runtime option is a nice feature that really helps understanding the consequences of the PyEnum move. [ChangeLog][PySide6] The QEnum tests are enabled for both the old Qt Enums and the new Python Enums. Change-Id: I78a7473f4a86f8d2115acc56e4ed11cf135eb000 Pick-to: 6.3 Task-number: PYSIDE-1735 Reviewed-by: Christian Tismer <tismer@stackless.com>
* un-blacklist some forgotten entriesChristian Tismer2022-04-291-4/+0
| | | | | | Change-Id: I537f078e7b7fff6ee30c5659c900ad24dbff23cb Pick-to: 6.3 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* PyPySide: handle signature with the new "builtin method" typeChristian Tismer2022-03-151-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | PyPy never had a distinction between normal methods and builtin methods like Python has by PyCFunction. Not immediately on our demand, but because the NumPy extension grew a problem out of exactly the same fact, a new "builtin method" was created. Using this new type, three errors concerning signatures could be resolved: sample::renaming QtWidgets::signature_test QtQml::qqmlnetwork_test [ChangeLog][PySide6] The new PyPy "builtin method" is now adopted and handled correctly in the signature module. Task-number: PYSIDE-1843 Task-number: PYSIDE-535 Change-Id: I462fe67fe63453fc214e332645dba60a1d399f5c Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Blacklist testmodifydocumentation for macOSFriedemann Kleint2022-03-141-0/+2
| | | | | | | | | | 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-4/+5
| | | | | | | | | | | | | | | | | | 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>
* PyPySide: fix a bunch of pseudo-errorsChristian Tismer2022-03-111-20/+0
| | | | | | | | | | | | | These ten errors could be removed. There were more GC calls needed. Sometimes, calling GC twice did the trick. We are now at 14 core errors, 18 in total :) Task-number: PYSIDE-1843 Task-number: PYSIDE-535 Change-Id: Iafb3f93682639ba28e5326f3b8cdebf6670a7b69 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* PyPySide: Blacklist all remaining bugs in order to publishChristian Tismer2022-03-091-5/+58
| | | | | | | | | | | | | | | | | | PyPy is very far and usable in almost all examples. Still, about 25 bugs are remaining which are hiding deep inside and can only over time and with some luck be found. Blacklist those remaining errors in order to publish PyPy's 96% status. Currently 27 of 657 tests fail. (24 in the core tests) [ChangeLog][PySide6] PyPy is by 96% ready. We publish it in the current state, hoping to solve the rest over time. Task-number: PYSIDE-535 Change-Id: I718747c09709b5e040b7b95e86a8ac95dfd89cf4 Reviewed-by: Simo Fält <simo.falt@qt.io>
* Blacklist qthread_testFriedemann Kleint2022-02-241-0/+2
| | | | | | | | | | | | | | | Observed to crash with Python 3.6 on Linux: Fatal Python error: take_gil: NULL tstate Current thread 0x00007f3d4f596700 (most recent call first): Thread 0x00007f3d597b8b80 (most recent call first): File "sources/pyside6/tests/QtCore/qthread_test.py", line 101 in testSignals Pick-to: 6.2 Change-Id: Ibb57ae06d530799b94d27e8c54b9bc387c2916ba Reviewed-by: Christian Tismer <tismer@stackless.com>
* Tests: Remove blacklisting after recent stabilization fixesFriedemann Kleint2021-12-081-12/+0
| | | | | | Change-Id: I7555127e772be15267800ecf5bb1e13c72226953 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* PyPySide: Skip AssertRaises which needs a PyPy fixChristian Tismer2021-12-061-0/+5
| | | | | | | | | | | | Seven tests create an RPython: NotImplemented error that needs fixing in PyPy. We skip the error until solved, but keep an entry in blacklist.txt in order to not forget about the fact. This brings the error count from 30 down to 23. Task-number: PYSIDE-535 Change-Id: I36c8d3e3e4b5b24508bae884a392f976c41964da Reviewed-by: Christian Tismer <tismer@stackless.com>
* PyPySide: Fix BindingManager::getOverride and othersChristian Tismer2021-11-091-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | PyPy has a major difference when it comes to distinguish PyCFunction and PyFunction/PyMethod. PyCFunction is not differentiated in PyPy and its handling collapses with PyMethod handling. A simple way to emulate the difference is by a redefinition that uses a check for __module__, that does not exist for builtins. Observation: There are quite a number of false callbacks in Qt that create wrong notifications. Before this error was fixed, these errors were reported by the error handler. When handled correctly, these spurious notifications are ignored, again. The effect of this change is very good: 76 errors left instead of 99. [ChangeLog][shiboken6] The override handling for PyPy was fixed because PyPy has a different understanding of builtin functions. Task-number: PYSIDE-535 Change-Id: I7d7419135a50df9a540e953b75890ca2ec28993c Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* PyPySide: add it as a true new build targetChristian Tismer2021-10-281-0/+2
| | | | | | | | | | | | | | | | | | 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>
* PySide6: Work around uic feature test failureFriedemann Kleint2021-07-291-3/+0
| | | | | | | | | | | | | | Use QCoreApplication.process_events() instead of qApp..process_events() which causes: AttributeError: 'PySide6.QtWidgets.QApplication' object has no attribute 'process_events' Amends 9b5fa60d1fed5025e97c393ba1bab80f81ba833a. Task-number: PYSIDE-1626 Pick-to: 6.1 Pick-to: 5.15 Change-Id: I7a268c8fa5b699813dfcb37a3093bd897fec381c Reviewed-by: Christian Tismer <tismer@stackless.com>
* feature: fix the UIC switching problemChristian Tismer2021-07-281-0/+3
| | | | | | | | | | | | | | | | | | | | | The BindingManager::getOverride function computes the current switch state from information of a type object. But the type object must first be updated in case a switch has happened. The solution was an extra update call at the beginning of the function. This solution _always_ works, with or without inheritance, for Python >= 3.7. [ChangeLog][shiboken6] Coexistence of different feature selections works now, especially for UIC files and inheritance. Fixes: PYSIDE-1626 Pick-to: 6.1 Pick-to: 5.15 Change-Id: I577331cfb2d7511110d1e16e729bed80985340a0 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* PySide: fix QItemSelection default and QItemSelection.__add__Christian Tismer2021-07-201-3/+0
| | | | | | | | | | | | | | | | | | | | | | QItemSelection with no argument should create an empty selector. This worked in Qt5. In Qt6, everything works but the empty argument. Without further analysis, this might be related to the new [default] tag found in the Qt6 QItemSelection documentation? Fixing this bug leads directly to the add operator, which returns a list instead of a combined QItemSelection. Fixed by removing `operator+(list<QItemSelectionRange>)` and re-adding it with QItemSelection Unrelated, occurred during bug hunting. Task-number: PYSIDE-535 Change-Id: Ie5b881659e54fc0eebc8c9903df6e14eb2788565 Pick-to: 6.1 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Update blacklist.txt for errors in debug modeChristian Tismer2021-06-161-0/+5
| | | | | | | | | | | | | | There are two hard-to-solve refcounting bugs that are only detected in debug mode. For the new Windows debug test setup (hopefully coming soon), these errors need to be ignored. Task-number: PYSIDE-68 Task-number: PYSIDE-79 Change-Id: I86bb3fa06cc201e5c123aa3f7cff1d814d44e242 Pick-to: 6.1 Reviewed-by: Christian Tismer <tismer@stackless.com>
* Test blacklist: Re-add macOS failuresFriedemann Kleint2021-04-291-0/+4
| | | | | | | | Partially revert 29edb488705c1498f67ff7c1958b27d617136da0, which was integrated without macOS checks. Change-Id: If74902a1944fc0bc106ab2f9d689a1235d075f1f Reviewed-by: Christian Tismer <tismer@stackless.com>
* Clean test blacklistFriedemann Kleint2021-04-281-65/+0
| | | | | | | Remove tests that pass by trial and error. Change-Id: Ia4a1ca5c25ba4cddc882a29c580edc7c1b1957d1 Reviewed-by: Christian Tismer <tismer@stackless.com>
* move "shiboken6/shiboken6" to "shiboken6/Shiboken"Christian Tismer2021-02-061-3/+0
| | | | | | | | | | | | | | | | | | | | | Modifying the paths to work in the new way is a quite ambitious task. But doing so improves the overall project structure and makes imports unambiguous. This patch should not be applied alone but with move "shiboken6/shiboken6" to "shiboken6/Shiboken" temp The reworked version of this patch no longer has different structures in `build` and `install`. Tested with Python 3.6, 3.7, 3.8, 3.9 debug build Python 3.6 debug install Python 3.9 release install Task-number: PYSIDE-1497 Change-Id: Id9d816dd825907f9359651e7e2f69f54e1ba46c9 Reviewed-by: Christian Tismer <tismer@stackless.com>
* Blacklist Qt3DExtras::qt3dextras_test in win when ran in CISimo Fält2021-02-011-0/+1
| | | | | | Pick-to: 6.0 Change-Id: Iae2540ea863cc2e4c33ac3798aa05f3592c9b513 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* remove QBackingStore from qrasterwindow_test.pyChristian Tismer2020-12-151-2/+0
| | | | | | | | | | The QBackingStore part of qrasterwindow_test.py does not work on macOS. We remove this part of the test that should not even reside in PySide but is a Qt matter. Change-Id: I520a5fd1336850d3e3883bcccb9b6a4b2cdafeda Pick-to: 6.0 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Blacklist failing test cases with Qt6Simo Fält2020-12-081-0/+19
| | | | | Change-Id: I61af0ec073341d89d602aa600060a4d9cc4acb19 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* fix both qflags_test and the qflags cppgenerator codeChristian Tismer2020-12-031-3/+0
| | | | | | | | | | | | | | | | | | There was a years-old qflags test failing on Python 3. It was blacklisted with the comment "# Nested exception in Python 3" This was nonsense: The test was wrong also for Python 2. It just happened to work, because Python 2 had some weird errors leaking. The real bug was in missing error handling in cppgenerator.cpp . See the main description in the issue. Change-Id: Ia0f9466640e0eb33f1b8b26178d33f2be0bcb32f Task-number: PYSIDE-1442 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* PySide6: Fix test javascript_exceptions.pyFriedemann Kleint2020-11-271-2/+0
| | | | | | | It was using the old Qt Quick Controls 1. Change-Id: Ia1d6a884267fdcd8e3808b08bf1efa12eb62b4dd Reviewed-by: Christian Tismer <tismer@stackless.com>
* Blacklist failing tests for Qt 6Friedemann Kleint2020-11-191-0/+5
| | | | | | | | | Tested using Qt 6 beta 5. Task-number: PYSIDE-1339 Task-number: PYSIDE-904 Change-Id: I378770df929327aa8aa502751baac482702520d7 Reviewed-by: Christian Tismer <tismer@stackless.com>
* Rename PySide2 to PySide6Friedemann Kleint2020-11-021-1/+1
| | | | | | | | Adapt CMake files, build scripts, tests and examples. Task-number: PYSIDE-904 Change-Id: I845f7b006e9ad274fed5444ec4c1f9dbe176ff88 Reviewed-by: Christian Tismer <tismer@stackless.com>
* Partial revert "Use qt5 5.14.1 in CI"Simo Fält2020-02-061-0/+3
| | | | | | | | | | This reverts commit 422546c884b9115cc2f1ba35bca36cc09a0a71ec. 5.14 should follow default Qt5 branch again, but we still want to update the PyInstaller to 3.6. Change-Id: I801d1a40192b2ee2873ca04710c788879a35532d Reviewed-by: Christian Tismer <tismer@stackless.com> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
* Prospective fix for flaky smart_pointer_test.pyFriedemann Kleint2020-01-301-3/+1
| | | | | | | | | | | | | | | | | | | | The test has been observed to fail apparently since the result was not collected. Traceback (most recent call last) File "sources/shiboken2/tests/smartbinding/smart_pointer_test.py", line 82, in testObjSmartPointer self.assertEqual(integerCount(), 1) AssertionError 2 != 1 File "sources/shiboken2/tests/smartbinding/smart_pointer_test.py", line 154, in testSmartPointersWithNamespace self.assertEqual(integerCount(), 2) AssertionError 3 != 2 Enforce a garbage collection to ensure the object is deleted. Task-number: PYSIDE-454 Change-Id: I85baa059319a5286f94a5607c4de32bfc50ae0e0 Reviewed-by: Christian Tismer <tismer@stackless.com>
* Blacklist failing QtPositioning testFriedemann Kleint2019-07-031-1/+5
| | | | | | Task-number: QTBUG-66304 Change-Id: Ia6b02492c138aadefdf5c58c572bae54da7008c8 Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* Blacklist failing positioning autotest on WindowsAlexandru Croitor2018-11-231-0/+3
| | | | | | | | Looks like a qt5.git upgrade broke something. Change-Id: I57ec39b2ce2154745bb49028b5bf65dd87dcb34f Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* Blacklist flaky test web_engine_custom_schemeChristian Tismer2018-07-231-0/+5
| | | | | | | | | | | This test has failed three times until it passed. We therefore blacklisted it on all platforms. See also the bug report. Task-number: PYSIDE-754 Change-Id: Ieb84eb6605d309eb3963fbc867fcf8f6fc497a3e Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
* Blacklist QtCore/qfileread_test, Qt3DExtras/qt3dextras_test.py on macOSFriedemann Kleint2018-05-041-0/+3
| | | | | | Task-number: PYSIDE-431 Change-Id: I31deef0dc12a4b3ce11a6300c8594598d78c4712 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
* Blacklist Qt3DExtras/qt3dextras_test.py on LinuxFriedemann Kleint2018-02-011-0/+2
| | | | | | | | | Complements 458c258fbaf3b24ffa0132093be4d6af2f8dfd. Task-number: PYSIDE-431 Task-number: PYSIDE-487 Change-Id: Ia432097722eb87bb74d08b81e9b304edcec4fe81 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
* Merge remote-tracking branch 'origin/5.6' into 5.9Friedemann Kleint2018-01-051-3/+0
|\ | | | | | | Change-Id: I254cc725505349e73c7abc290afc7abb85156997
| * testrunner 5: Improve the algorithmChristian Tismer2017-12-211-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Testrunner checks if it is running in COIN. If so, it runs each tested project 5 times and reports an error if 3 errors were found in a test function and not blacklisted. The time is measured, so we know if we can run all the tests five times or if we can run only the failed tests. At the moment, the option COIN_RERUN_FAILED_ONLY is activated by default. We can configure it by setting to false. Since this change turns the registry existence test into a flaky test (te tests generates it's missing file in the first run), the registry existence test is no more blacklisted. We simulate our own tee command now with decorated output. Task-number: PYSIDE-578 Change-Id: I6390cd50398a97a168c85c6bb778984c6a5b90fc Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
| * blacklist.txt: Remove duplicate entryFriedemann Kleint2017-12-211-4/+0
| | | | | | | | | | Change-Id: Ie1b0e43f876cb4ac4228457ccb49ab43e63affe1 Reviewed-by: Christian Tismer <tismer@stackless.com>
* | Merge remote-tracking branch 'origin/5.6' into 5.9Friedemann Kleint2017-12-211-2/+4
|\| | | | | | | Change-Id: I78039827d32c1d4d540a8b1b2afd4841e40d5c2c
| * Fix QtCore test bug829 to run on WindowsFriedemann Kleint2017-12-191-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The test used Python functionality to create a temporary file which caused an access error on Windows, apparently due to the file still being open. Besides, the temporary file was leaked. Rewrite using QTemporaryFile and make sure the file is closed and the QTemporaryFile is deleted before using it and delete it in __del__(). Task-number: PYSIDE-431 Change-Id: I5d63e76ead7169d9f3f2267ee53aa91b601a3968 Reviewed-by: Christian Tismer <tismer@stackless.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-21 10:17:28 +0000