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

ARMHF: pollard_brent_single....FAIL : Pollard Rho failed too many times (106 times) #786

Closed
SnarkBoojum opened this issue Jul 4, 2020 · 13 comments · Fixed by #795
Closed

Comments

@SnarkBoojum
Copy link

The armhf platform is broken because of the above message.

@thofma
Copy link
Contributor

thofma commented Jul 13, 2020

@SnarkBoojum Could you sponsor @tthsqe12 for a guest account on the arm hf server?

@SnarkBoojum
Copy link
Author

I wanted to try a git bisect, but the old version tags are gone, and it looks like a few of the commits don't even build, so it ended fast.

@wbhart
Copy link
Collaborator

wbhart commented Jul 20, 2020

Were you able to get access for @tthsqe12 ?

@tthsqe12
Copy link
Contributor

I have no access

@SnarkBoojum
Copy link
Author

No access requested, no access granted... Here's the procedure ; I can sponsor but you have to provide some information...

@tthsqe12
Copy link
Contributor

We are trying something a bit simpler first.

@SnarkBoojum
Copy link
Author

Can I help?

@tthsqe12
Copy link
Contributor

I don't think so. We will know in a few hours if we really need access to the machine that was failing. Did you observe this consistently failing at every try, or was it more a Heisenbug?

@SnarkBoojum
Copy link
Author

I would say it fails consistently.

@wbhart
Copy link
Collaborator

wbhart commented Jul 20, 2020

@tthsqe12 it passes on x86 32 bit if that's what you are wondering. It really does seem to be ARM specific, and most likely something in longlong.h. I looked through the code for anything else it could be and came up blank.

@tthsqe12
Copy link
Contributor

We will most likely be able to fix this ourselves by tomorrow or the day after. By the way, the other two failures on mips and something else should be fixed.

@wbhart
Copy link
Collaborator

wbhart commented Jul 21, 2020

Should be fixed in the flint-2.6 branch now. We'll issue 2.6.1 as soon as some of the other recent bug tickets are closed.

@SnarkBoojum
Copy link
Author

I'll wait for 2.6.1 ; thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants