Before f3b0f220a78d4e5a5b94b46e931779d755ac19ce when getting the details of a symlink a regular QT_STAT mimicking stat() was used.
Details
- Reviewers
dfaure - Group Reviewers
Frameworks - Commits
- R241:dfbc18403297: Use regular stat when resolving a symlink
ctest
Diff Detail
- Repository
- R241 KIO
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Glad that the unittest caught an actual bug for once :-)
Yes we'd all love pre-merge CI checks, but that won't happen with phabricator. I hear rumours of a migration to gitlab at some point, which should surely help.
The Gitlab migration is in planning and preparation stages, so should happen sometime in the next couple of months.
I can't wait for gitlab migration.
phabricator is quite nice but not as common as a git-PR based workflow.
https://build.kde.org/view/OS - Windows/job/Frameworks/job/kio/job/kf5-qt5 SUSEQt5.10/95 Will confirm if this is fixed.
Regressions are fixed :
https://build.kde.org/view/OS%20-%20Windows/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.10/95/testReport/junit/projectroot/autotests/kiowidgets_kdirmodeltest/history/
https://build.kde.org/view/OS%20-%20Windows/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.10/87/testReport/junit/projectroot/autotests/kiocore_jobtest/history/
There are 2 failures still on the build though.