RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

scalar: scalar.c:148: main: Assertion `-1 == res' failed

This happens when the testcase is run as root.
setuid (0) is expected to FAIL.

This is just a testcase issue. It would be nice to make it robust against running as root.
But it is harmless. Better to not run the testcase as root in the first place.

This is similar to the arm64 case https://bugzilla.redhat.com/show_bug.cgi?id=1652488

commit abc09f23e1ad55a07beb827aef969acfe6c496ef
Author: Mark Wielaard <mark>
Date:   Mon May 20 13:08:41 2019 +0200

    Make memcheck/tests/x86-linux/scalar test work under root.
    
    Running the testsuite as root isn't really recommended.
    But lets not make tests fail unnecessarily when running as root.
    Similar to the arm64-linux/scalar fixes. Plus 32bit variants that
    don't exist on arm64.
    
    Pass really invalid arguments to setuid[32], setgid[32], acct, fchown[32].
    Make setresgid[32], setresuid[32], setregid[32], setreuid[32] always succeed

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:0986