New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New compiler failures on Fedora 33 #4093
Comments
Here are all the comilier errors and warnings: ldap/servers/plugins/replication/repl_extop.c: In function 'multimaster_extop_EndNSDS50ReplicationRequest':
ldap/servers/plugins/replication/cl5_api.c:686:12: warning: 'rc' may be used uninitialized in this function [-Wmaybe-uninitialized]
In function 'strncpy',
/usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound depends on the length of the source argument [-Wstringop-overflow=] In file included from /usr/include/string.h:519,
/usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound depends on the length of the source argument [-Wstringop-overflow=] In file included from /usr/include/string.h:519,
In function 'strncpy',
In function 'strncpy',
warning: Tag 'PERL_PATH' at line 2058 of file '/builddir/build/BUILD/389-ds-base-2.0.1/docs/slapi.doxy' has become obsolete. |
Description: Update the doxy file (doxygen), fix compiler warnings (x86_64, arm, and s390x), and update Rust cargo file. relates: 389ds#4093 Reviewed by: firstyear, spichugi, & progier(Thanks!!!)
Description: Update the doxy file (doxygen), fix compiler warnings (x86_64, arm, and s390x), and update Rust cargo file. relates: #4093 Reviewed by: firstyear, spichugi, & progier(Thanks!!!)
Bug Description: Once some compiler warnings were fixed it accidentally fixed the modrdn behavior. Previously the modrdn code accidentally ignored errors that the test case was taking for granted. Once these checks were properly inforced the teset case started to fail. Fix Description: Revise test case to "properly" check modrdn operations by creating the Managed Entry before assignign it to an entry, and then check for the revise managhed entry DN after the modrdn takes place. Also, improved CI debugging logging settings relates: 389ds#4093 Reviewed by: spichugi(Thanks!)
Bug Description: Once some compiler warnings were fixed it accidentally fixed the modrdn behavior. Previously the modrdn code accidentally ignored errors that the test case was taking for granted. Once these checks were properly inforced the teset case started to fail. Fix Description: Revise test case to "properly" check modrdn operations by creating the Managed Entry before assignign it to an entry, and then check for the revise managhed entry DN after the modrdn takes place. Also, improved CI debugging logging settings relates: #4093 Reviewed by: spichugi(Thanks!)
Bug Description: Once some compiler warnings were fixed it accidentally fixed the modrdn behavior. Previously the modrdn code accidentally ignored errors that the test case was taking for granted. Once these checks were properly inforced the teset case started to fail. Fix Description: Revise test case to "properly" check modrdn operations by creating the Managed Entry before assignign it to an entry, and then check for the revise managhed entry DN after the modrdn takes place. Also, improved CI debugging logging settings relates: #4093 Reviewed by: spichugi(Thanks!)
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/51040
Issue Description
The text was updated successfully, but these errors were encountered: