-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
tox.ini: Add raspbian-buster #29091
Comments
comment:1
Attachment: fplll-5.3.2.log I have added |
comment:2
Moving tickets to milestone sage-9.2 based on a review of last modification date, branch status, and severity. |
Changed keywords from none to raspberry |
comment:4
This might be fixed upstream, can you try again? See fplll/fplll#418 |
comment:5
Replying to @malb:
Building sage-9.1 I get still the same ailure:
|
comment:6
Sorry that fix isn't in Sage (or an upstream release yet). I meant trying upstream |
Upstream: Reported upstream. Developers acknowledge bug. |
This comment has been minimized.
This comment has been minimized.
comment:7
I opened this issue in the fplll issue tracker
but apparently this issue might have been relevant
and it was fixed in Apr 2020 by this pull request
The current latest release, fplll 5.3.2, is from Jan 2020. |
Branch: u/mkoeppe/raspian-buster |
Commit: |
comment:10
Tests running at https://github.com/mkoeppe/sage/actions/runs/146618564 |
comment:11
Running this on my Mac, I was able to reproduce the error:
|
Changed author from jsp to Matthias Koeppe |
comment:13
Replying to @mkoeppe:
Actually, it is
which will also work on Linux Docker. Tests with fplll@master run at https://github.com/mkoeppe/fplll/actions/runs/146958161 |
comment:14
Replying to @mkoeppe:
It says:
Could a tox environment install most dependencies using Conda via miniforge? Miniforge provides Conda on ARM: |
comment:15
fplll@master on This confirms that master contains the correct fix. |
comment:16
|
Changed upstream from Reported upstream. Developers acknowledge bug. to Fixed upstream, but not in a stable release. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits: |
comment:19
Removed 714bdce from the branch - the build is so slow because of the emulation that it does not make sense to test the sage distribution on this platform on GH Actions. |
comment:20
See https://github.com/fplll/fplll/releases/tag/5.3.3 and #30021. |
Dependencies: #30021 |
Changed upstream from Fixed upstream, but not in a stable release. to Completely fixed; Fix reported upstream |
This comment has been minimized.
This comment has been minimized.
comment:27
Works for me on a Raspberry Pi 4 4GB, Raspbian Buster |
comment:28
Here you can read more about how we address portability testing. One does not need an actual Raspberry Pi. https://doc.sagemath.org/html/en/developer/portability_testing.html#testing-sage-on-a-different-platform-using-docker |
comment:29
I noted on some other ticket that GitHub Actions offer an ARM platform. |
comment:30
Reviewer name is missing |
Reviewer: Jaap Spies |
Changed branch from u/mkoeppe/raspian-buster to |
On Raspberry Pi 4 4GB on Raspbian Buster build failed with fplll:
This is fixed by upgrading FPLLL in #30021.
In this ticket, we add Docker-based testing for the platform
raspbian-buster-armhf
so that it can be verified that FPLLL now builds on this platform by the following:Depends on #30021
Upstream: Completely fixed; Fix reported upstream
CC: @malb @slel @fchapoton @kliem
Component: build
Keywords: raspberry
Author: Matthias Koeppe
Branch/Commit:
1b4c497
Reviewer: Jaap Spies
Issue created by migration from https://trac.sagemath.org/ticket/29091
The text was updated successfully, but these errors were encountered: