From: Mark Wielaard <mark@klomp.org>
To: annobin@sourceware.org
Subject: s390x build test failure for GO FIPS
Date: Mon, 25 Dec 2023 18:09:57 +0100 [thread overview]
Message-ID: <20231225170957.GH6896@gnu.wildebeest.org> (raw)
Since commit 08bc2832527f42b517f2d550e8ada452b4ad21ee
12.24: Annocheck: Changes GO FIPS test to look for CGO_ENABLED markers
The s390x CI builder has been failing:
https://builder.sourceware.org/buildbot/#/builders/annobin-fedora-s390x
The tests/test-suite.log looks as follows:
===================================================
Binary Annotations 12.0: tests/test-suite.log
===================================================
# TOTAL: 27
# PASS: 26
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: go-fips-test
==================
~/annobin/tests/tmp_go-fips ~/annobin/tests
go-fips: Running: go build no-use-crypto.go
go-fips: Checking a GO binary that does not use crypto
go-fips: Running: ../../annocheck/annocheck -v --skip-all --test-fips no-use-crypto
Hardened: no-use-crypto: skip: fips test because binary did not load a crypto library
go-fips: PASS: annocheck ignored a GO binary that does not use crypto
go-fips: Running: CGO_ENABLED=1 go build use-crypto.go
go-fips: Checking a FIPS-compliant GO binary
go-fips: FAIL: annocheck did not detect a FIPS compliant GO binary
annocheck: Version 12.34.
Hardened: use-crypto: warn: Unable to determine the binary's producer from it's DW_AT_producer string.
Hardened: use-crypto: FAIL: fips test because the binary was not built with CGO_ENABLED=1
Hardened: use-crypto: info: For more information visit: https://sourceware.org/annobin/annobin.html/Test-fips.html
Hardened: use-crypto: Overall: FAIL.
~/annobin/tests
FAIL go-fips-test (exit status: 1)
Note that this is a Fedora 38 system with:
$ alternatives --display go
go - status is auto.
link currently points to /usr/bin/go.gcc
/usr/bin/go.gcc - priority 92
follower gofmt: /usr/bin/gofmt.gcc
/usr/lib/golang/bin/go - priority 90
follower gofmt: /usr/lib/golang/bin/gofmt
Current `best' version is /usr/bin/go.gcc.
next reply other threads:[~2023-12-25 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-25 17:09 Mark Wielaard [this message]
2024-01-02 10:30 ` Nick Clifton
2024-01-02 12:06 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231225170957.GH6896@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=annobin@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).