Re: KDE Gear projects with failing CI (master) (18 February 2025)
El dimecres, 19 de febrer del 2025, a les 9:58:30 (Hora estàndard del Centre d’Europa), Ingo Klöcker va escriure: > On Mittwoch, 19. Februar 2025 03:05:06 Mitteleuropäische Normalzeit Justin > > Zobel wrote: > > On 19/2/25 10:37, Albert Astals Cid wrote: > > > Please work on fixing them, otherwise i will remove the failing CI jobs > > > on > > > their 4th failing week, it is very important that CI is passing for > > > multiple reasons. > > > > > > Good news: 2 repositories were fixed > > > > > > Bad news: 12 repositories started failing > > > > > > kate - NEW > > > > > > *https://invent.kde.org/utilities/kate/-/pipelines/891876 > > > > > >* flatpak failed > > > > > > kwordquiz - NEW > > > > > > *https://invent.kde.org/education/kwordquiz/-/pipelines/890572 > > > > > >* flatpak failed > > > > > > lokalize - NEW > > > > > > *https://invent.kde.org/sdk/lokalize/-/pipelines/891879 > > > > > >* flatpak failed > > > > > > kteatime - NEW > > > > > > *https://invent.kde.org/utilities/kteatime/-/pipelines/886431 > > > > > >* flatpak failed > > > > > > audiotube - NEW > > > > > > *https://invent.kde.org/multimedia/audiotube/-/pipelines/890981 > > > > > >* flatpak failed > > > > > > keysmith - NEW > > > > > > *https://invent.kde.org/utilities/keysmith/-/pipelines/891694 > > > > > >* flatpak failed > > > > > > koko - NEW > > > > > > *https://invent.kde.org/graphics/koko/-/pipelines/891687 > > > > > >* flatpak failed > > > > > > telly-skout - NEW > > > > > > *https://invent.kde.org/utilities/telly-skout/-/pipelines/891394 > > > > > >* flatpak failed > > > > > > francis - NEW > > > > > > *https://invent.kde.org/utilities/francis/-/pipelines/891695 > > > > > >* flatpak failed > > > > All fixed: > > francis > > koko > > keysmith > > audiotube > > lokalize > > kate > > > > The other flatpak failures need more investigation. > > The other flatpaks are now also fixed: > kwordquiz > kteatime > telly-skout > > @Albert: Part of the problem was that you have triggered the flatpak jobs on > old pipelines (at least for kwordquiz and kteatime) with an obsolete > definition of the flatpak job. To avoid such problems you should always > trigger a new pipeline instead of using an old pipeline even if it takes > more time to run a full pipeline. In the end it may cost less people-time. This is the first time i have such a problem. Restarting the whole pipeline (which may include compiling macos craft which is mega slow beacuse we only have 1 builder) is what I did earlier and I ended up deciding it took too much CPU time (and my time waiting for things to finish to build). Cheers, Albert > > Regards, > Ingo
[ANNOUNCE] CMake 4.0.0-rc1 is ready for testing
I am proud to announce the first CMake 4.0 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v4.0 Release notes appear below and are also published at https://cmake.org/cmake/help/v4.0/release/4.0.html Release milestone is available at: https://gitlab.kitware.com/cmake/cmake/-/milestones/160 Some of the most significant changes in CMake 4.0 are: * The "CMAKE_POLICY_VERSION_MINIMUM" variable was added to help packagers and end users try to configure existing projects that have not been updated to work with supported CMake versions. * The "$" generator expression gained the "NATIVE_PATH" operation to convert a CMake path into a native one. * Compatibility with versions of CMake older than 3.5 has been removed. Calls to "cmake_minimum_required()" or "cmake_policy()" that set the policy version to an older value now issue an error. Note that calls to those commands can still support older versions of CMake by using their "VERSION" arguments' "..." syntax. This requires only the "" version of CMake, but when running a newer version, sets policies up to the "" version. * On macOS with Ninja Generators and Makefile Generators, when a compiler is found in "/usr/bin", it is now used as-is and is no longer mapped to the corresponding compiler inside Xcode. * Builds targeting macOS no longer choose any SDK or pass an "-isysroot" flag to the compiler by default. Instead, compilers are expected to choose a default macOS SDK on their own. In order to use a compiler that does not do this, users must now specify "-DCMAKE_OSX_SYSROOT=macosx" when configuring their build. * Precompiled SunOS "sparc" and "i386" binaries are now provided on cmake.org. CMake 4.0 Release Notes *** Changes made since CMake 3.31 include the following. New Features File-Based API -- * The "cmake-file-api(7)" "codemodel" version 2 "version" field has been updated to 2.8. * The "cmake-file-api(7)" "codemodel" version 2 "target" object gained a new "debugger" field. Command-Line * The "cmake --link-no-warning-as-error" option was added to suppress the effects of the "LINK_WARNING_AS_ERROR" target property and "CMAKE_LINK_WARNING_AS_ERROR" variable. * The "cmake --project-file" option was added to specify an alternate filename for "CMakeLists.txt" files. This is intended for temporary use by developers during an incremental transition and not for publication of a final product. CMake will always emit a warning when the project file is anything other than "CMakeLists.txt". Commands * The "target_link_libraries()" command now supports the "LINKER:" prefix. Variables - * The "AIX" and "CMAKE_HOST_AIX" variables are now set to true when the target or host system is AIX, respectively. * Linker flag variables learned to support the "LINKER:" prefix: * "CMAKE_EXE_LINKER_FLAGS" * "CMAKE_EXE_LINKER_FLAGS_" * "CMAKE_SHARED_LINKER_FLAGS" * "CMAKE_SHARED_LINKER_FLAGS_" * "CMAKE_MODULE_LINKER_FLAGS" * "CMAKE_MODULE_LINKER_FLAGS_" See policy "CMP0181". * The "CMAKE_EXECUTE_PROCESS_COMMAND_ERROR_IS_FATAL" variable was added to specify the "execute_process()" command's default "COMMAND_ERROR_IS_FATAL" behavior. * The "CMAKE__LINK_MODE" and "CMAKE__DEVICE_LINK_MODE" variables were added to provide information on how the link step is done. * The "CMAKE_LINK_WARNING_AS_ERROR" variable and corresponding "LINK_WARNING_AS_ERROR" target property were added to link using a linker-specific flag to treat warnings as errors. * The "CMAKE_MSVC_RUNTIME_CHECKS" variable and "MSVC_RUNTIME_CHECKS" target property were introduced to select runtime checks for compilers targeting the MSVC ABI. See policy "CMP0184". * The "CMAKE_POLICY_VERSION_MINIMUM" variable was added to help packagers and end users try to configure existing projects that have not been updated to work with supported CMake versions. * The "CMAKE_XCODE_SCHEME_LLDB_INIT_FILE" variable and corresponding "XCODE_SCHEME_LLDB_INIT_FILE" target property were added to tell the "Xcode" generator what to put in the scheme's "LLDB Init File" setting. * The "CMAKE_XCODE_SCHEME_TEST_CONFIGURATION" variable and corresponding "XCODE_SCHEME_TEST_CONFIGURATION" target property were added to tell the "Xcode" generator what to put in the scheme's "Build Configuration" setting for the test action. Properties -- * The "DEBUGGER_WORKING_DIRECTORY" target property and corresponding "CMAKE_DEBUGGER_WORKING_DIRECTORY" variable were added to tell generators what debugger working directory should be set for targets. * The "STATIC_LIBRARY_OPTIONS" target property now supports an "ARCHIVER:" prefix to pass options to the archiver through the compiler driver in a portable way. * The "Swift_MODULE_DIRECTORY" target property now supports "generato
Re: KDE Gear projects with failing CI (master) (18 February 2025)
On Mittwoch, 19. Februar 2025 22:12:58 Mitteleuropäische Normalzeit Albert Astals Cid wrote: > El dimecres, 19 de febrer del 2025, a les 9:58:30 (Hora estàndard del Centre > d’Europa), Ingo Klöcker va escriure: > > @Albert: Part of the problem was that you have triggered the flatpak jobs > > on old pipelines (at least for kwordquiz and kteatime) with an obsolete > > definition of the flatpak job. To avoid such problems you should always > > trigger a new pipeline instead of using an old pipeline even if it takes > > more time to run a full pipeline. In the end it may cost less > > people-time. > > This is the first time i have such a problem. > > Restarting the whole pipeline (which may include compiling macos craft which > is mega slow beacuse we only have 1 builder) is what I did earlier and I > ended up deciding it took too much CPU time (and my time waiting for things > to finish to build). You are right. It probably doesn't happen that often that a job in a pipeline gets outdated (provided that new pipelines are triggered more or less frequently). What's your current approach? Do you look at the last master (or release/ xx.yy) pipeline that ran for a project and then just re-trigger failed jobs? Regards, Ingo signature.asc Description: This is a digitally signed message part.
Re: KDE Gear projects with failing CI (release/24.12) (18 February 2025)
On Mittwoch, 19. Februar 2025 00:44:29 Mitteleuropäische Normalzeit Albert Astals Cid wrote: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for multiple > reasons. > > > Good news: 2 fixed > > Bad news: 1 started failing > > > kdenlive - NEW > * https://invent.kde.org/multimedia/kdenlive/-/pipelines/890991 > * craft window build fails Looks like Qt has a problem with MinGW if find_package(Qt6 ...) is called twice as done by breeze (once in top-level CMakeLists.txt and once in cursors/src/ kcursorgen/CMakeLists.txt): CMake Error at C:/gitlab/craft/windows-mingw_64-gcc/lib/cmake/ Qt6EntryPointPrivate/Qt6EntryPointMinGW32Target.cmake:4 (add_library): add_library cannot create imported target "EntryPointMinGW32" because another target with the same name already exists. Regards, Ingo signature.asc Description: This is a digitally signed message part.
Re: KDE Gear projects with failing CI (master) (18 February 2025)
On Mittwoch, 19. Februar 2025 03:05:06 Mitteleuropäische Normalzeit Justin Zobel wrote: > On 19/2/25 10:37, Albert Astals Cid wrote: > > Please work on fixing them, otherwise i will remove the failing CI jobs on > > their 4th failing week, it is very important that CI is passing for > > multiple reasons. > > > > Good news: 2 repositories were fixed > > > > Bad news: 12 repositories started failing > > > > kate - NEW > > *https://invent.kde.org/utilities/kate/-/pipelines/891876 > >* flatpak failed > > > > kwordquiz - NEW > > *https://invent.kde.org/education/kwordquiz/-/pipelines/890572 > >* flatpak failed > > > > lokalize - NEW > > *https://invent.kde.org/sdk/lokalize/-/pipelines/891879 > >* flatpak failed > > > > kteatime - NEW > > *https://invent.kde.org/utilities/kteatime/-/pipelines/886431 > >* flatpak failed > > > > audiotube - NEW > > *https://invent.kde.org/multimedia/audiotube/-/pipelines/890981 > >* flatpak failed > > > > keysmith - NEW > > *https://invent.kde.org/utilities/keysmith/-/pipelines/891694 > >* flatpak failed > > > > koko - NEW > > *https://invent.kde.org/graphics/koko/-/pipelines/891687 > >* flatpak failed > > > > telly-skout - NEW > > *https://invent.kde.org/utilities/telly-skout/-/pipelines/891394 > >* flatpak failed > > > > francis - NEW > > *https://invent.kde.org/utilities/francis/-/pipelines/891695 > >* flatpak failed > > All fixed: > francis > koko > keysmith > audiotube > lokalize > kate > > The other flatpak failures need more investigation. The other flatpaks are now also fixed: kwordquiz kteatime telly-skout @Albert: Part of the problem was that you have triggered the flatpak jobs on old pipelines (at least for kwordquiz and kteatime) with an obsolete definition of the flatpak job. To avoid such problems you should always trigger a new pipeline instead of using an old pipeline even if it takes more time to run a full pipeline. In the end it may cost less people-time. Regards, Ingo signature.asc Description: This is a digitally signed message part.
