Skip to content
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

[Flake] E2E: unclear errors in intrinsics_common.go #1604

Open
dtantsur opened this issue Mar 6, 2024 · 6 comments
Open

[Flake] E2E: unclear errors in intrinsics_common.go #1604

dtantsur opened this issue Mar 6, 2024 · 6 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@dtantsur
Copy link
Member

dtantsur commented Mar 6, 2024

Looks like this:

14:53:39  + make docker
14:53:39  cd hack/tools; go build -o /home/metal3ci/slave_root/workspace/metal3-bmo-e2e-test-pull/tools/bin/controller-gen sigs.k8s.io/controller-tools/cmd/controller-gen
14:53:40  # runtime/internal/sys
14:53:40  /usr/local/go/src/runtime/internal/sys/intrinsics_common.go:9:7: len8tab redeclared in this block
14:53:40  	/usr/local/go/src/runtime/internal/sys/intrinsics.go:76:7: other declaration of len8tab
14:53:40  /usr/local/go/src/runtime/internal/sys/intrinsics_common.go:32:6: Len64 redeclared in this block
14:53:40  	/usr/local/go/src/runtime/internal/sys/intrinsics.go:99:6: other declaration of Len64
14:53:40  /usr/local/go/src/runtime/internal/sys/intrinsics_common.go:50:7: m0 redeclared in this block
14:53:40  	/usr/local/go/src/runtime/internal/sys/intrinsics.go:117:7: other declaration of m0
14:53:40  /usr/local/go/src/runtime/internal/sys/intrinsics_common.go:51:7: m1 redeclared in this block
14:53:40  	/usr/local/go/src/runtime/internal/sys/intrinsics.go:118:7: other declaration of m1
14:53:40  /usr/local/go/src/runtime/internal/sys/intrinsics_common.go:52:7: m2 redeclared in this block
14:53:40  	/usr/local/go/src/runtime/internal/sys/intrinsics.go:119:7: other declaration of m2
14:53:40  /usr/local/go/src/runtime/internal/sys/intrinsics_common.go:55:6: OnesCount64 redeclared in this block
14:53:40  	/usr/local/go/src/runtime/internal/sys/intrinsics.go:122:6: other declaration of OnesCount64
14:53:40  /usr/local/go/src/runtime/internal/sys/intrinsics_common.go:86:6: LeadingZeros64 redeclared in this block
14:53:40  	/usr/local/go/src/runtime/internal/sys/intrinsics.go:153:6: other declaration of LeadingZeros64
14:53:40  /usr/local/go/src/runtime/internal/sys/intrinsics_common.go:89:6: LeadingZeros8 redeclared in this block
14:53:40  	/usr/local/go/src/runtime/internal/sys/intrinsics.go:156:6: other declaration of LeadingZeros8
14:53:40  /usr/local/go/src/runtime/internal/sys/intrinsics_common.go:92:6: Len8 redeclared in this block
14:53:40  	/usr/local/go/src/runtime/internal/sys/intrinsics.go:159:6: other declaration of Len8
14:53:40  /usr/local/go/src/runtime/internal/sys/intrinsics_common.go:101:6: Prefetch redeclared in this block
14:53:40  	/usr/local/go/src/runtime/internal/sys/intrinsics.go:200:6: other declaration of Prefetch
14:53:40  /usr/local/go/src/runtime/internal/sys/intrinsics_common.go:101:6: too many errors

Example: https://jenkins.nordix.org/view/Metal3/job/metal3-bmo-e2e-test-pull/340/console

@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Mar 6, 2024
@Rozzii
Copy link
Member

Rozzii commented Mar 6, 2024

/triage accepted

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Mar 6, 2024
@dtantsur
Copy link
Member Author

dtantsur commented Mar 6, 2024

/kind bug

@metal3-io-bot metal3-io-bot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 6, 2024
@mboukhalfa
Copy link
Member

mboukhalfa commented May 21, 2024

I am looking to update this, unfortunately the logs got lost (make me think to set another way to store logs persistently Jenkins can forget about them easily ) I will go through the bmo e2e recent runs fetching any occurrences

@mboukhalfa
Copy link
Member

Could not find similar error int the recent failed tests

@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 22, 2024
@Rozzii
Copy link
Member

Rozzii commented Aug 23, 2024

/remove-lifecycle stale

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

4 participants