[sage-release] Re: Sage 9.1.rc0 released

2020-04-14 Thread Matthias Köppe
On Monday, April 13, 2020 at 2:05:30 PM UTC-7, Matthias Köppe wrote:
>
> On Sunday, April 12, 2020 at 3:37:55 PM UTC-7, Volker Braun wrote:
> >
> > As always, you can get the latest beta version from the "develop" git 
> > branch. Alternatively, the self-contained source tarball is at 
> > http://www.sagemath.org/download-latest.html 
> >
> > 10ed24e3ed (trac/develop, tag: 9.1.rc0) Updated SageMath version to 
> 9.1.rc0
>
>  
> >
>
>
The above link leads to a page that summarizes an automatic test run of 
Sage on 100 platforms/system configurations (and gives access to full 
logs), using the testing framework described at 
https://wiki.sagemath.org/ReleaseTours/sage-9.1#Sage_9.1_Release_Tour, 
running on GitHub Actions.

Here's how to read it.

Each of the 100 items in the left pane represents a full build of Sage on a 
particular system configuration.
For example, 
- "docker (ubuntu-bionic, standard)" is a build with python 3 on ubuntu 
bionic with many system packages equivalent to our SPKGs installed;
- "docker (ubuntu-bionic, minimal)" is the same but only with a minimal set 
of system packages installed, so we build most of our standard packages 
from scratch.

A test item in the left pane is marked with a green checkmark in the left 
pane if "make build doc-html" finished without error.  (It also runs 
package testsuites and the Sage doctests but these are ; see below)

The right pane  ("Artifacts") offers archives of the logs for download.

Scrolling down in the right pane shows "Annotations":

* Red "check failure" annotations appear for each log file that contains a 
build error. For example, you might see:


[image: @github-actions]github-actions/ docker (fedora-28, standard)

artifacts/logs-commit-8ca1c2df8f1fb4c6d54b44b34b4d8320ebecb164-tox-docker-fedora-28-standard/logs/pkgs/sagetex-3.4.log#L1

    ERROR IN LOG FILE 
artifacts/logs-commit-8ca1c2df8f1fb4c6d54b44b34b4d8320ebecb164-tox-docker-fedora-28-standard/logs/pkgs/sagetex-3.4.log
 


* Yellow "check warning" annotations. There are 2 types of these:

  a) Package testsuite / Sage doctest failures

[image: @github-actions]github-actions/ docker (fedora-30, standard)

artifacts/logs-commit-8ca1c2df8f1fb4c6d54b44b34b4d8320ebecb164-tox-docker-fedora-30-standard/logs/ptest.log#L1

 TESTSUITE FAILURE IN LOG FILE 
artifacts/logs-commit-8ca1c2df8f1fb4c6d54b44b34b4d8320ebecb164-tox-docker-fedora-30-standard/logs/ptest.log
 


  b) Notices from ./configure about not finding equivalent system packages

[image: @github-actions]github-actions/ docker (fedora-31, standard)

artifacts/logs-commit-8ca1c2df8f1fb4c6d54b44b34b4d8320ebecb164-tox-docker-fedora-31-standard/config.log#L1

configure: notice: the following SPKGs did not find equivalent system packages: 
arb cbc cddlib cmake eclib ecm fflas_ffpack flint flintqs fplll givaro gp


Clicking on the annotations does not take you to a very useful place. To 
view details, click on one of the items in the pane. This changes the right 
pane to a log viewer. 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/d6ae6aa8-a5ae-41d7-800f-8f9fad46ca5b%40googlegroups.com.


Re: [sage-release] Sage 9.1.rc0 released

2020-04-14 Thread darwin doppelganger
"make sage" failed for the first time in several versions on my MacBook 
Pro, macOS Mojave,10.14.6. But after "make distclean", the build succeeded 
and then "make ptestlong" also completed successfully.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/a716bca5-d21e-4473-8bd0-9b2dfd440480%40googlegroups.com.


Re: [sage-release] Sage 9.1.rc0 released

2020-04-14 Thread 'Justin C. Walker' via sage-release



> On Apr 12, 2020, at 15:37 , Volker Braun  wrote:
> 
> As always, you can get the latest beta version from the "develop" git branch. 
> Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html 

Built, without problems, from fresh clones of the develop tree on three macOS 
systems:
 10.13.6 (18-core Xeon W, 2017 iMac Pro)
 10.14.6 (4-core Core i7, 2017 MBP)
 10.15.4 (9-core Core i9, 2019 MBP)

All tests passed (‘ptestlong’) on 10.13.6 and 10.15.4.
On 10.14.6, I had one failure, a timeout, which I attribute to my inability to 
persuade these systems to avoid sleeping.  I reran the testing (without a 
rebuild) with no failures.

Justin

PS: These are all more-or-less plain vanilla macOS systems, with no third-party 
package managers.

--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income

Experience is what you get
  when you don't get what you want.




-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/F446B60C-CAC0-4422-9477-0B2A6E224D15%40mac.com.


[sage-release] Re: Sage 9.1.rc0 released

2020-04-14 Thread Matthias Köppe
On Tuesday, April 14, 2020 at 7:42:26 AM UTC-7, Samuel Lelievre wrote:
>
>
> Le lundi 13 avril 2020 17:35:58 UTC+2, Matthias Köppe a écrit :
>>
>>
>> If you are testing on macOS, I recommend to merge #29404 and #29408
>>
> which missed the 9.1.rc0 bus and fix critical failures observed in 
>> 9.1.beta9.
>>
>
> Can you say how to merge #29404 and #29408
> on top of 9.1.rc0 to get things to work in macOS?
>

git trac fetch 29404 && git merge FETCH_HEAD
git trac fetch 29408 && git merge FETCH_HEAD



-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/10c5c037-b215-4ed0-a937-a9d4849f938e%40googlegroups.com.


[sage-release] Re: Sage 9.1.rc0 released

2020-04-14 Thread Samuel Lelievre


Le lundi 13 avril 2020 17:35:58 UTC+2, Matthias Köppe a écrit :
>
> On Sunday, April 12, 2020 at 3:37:55 PM UTC-7, Volker Braun wrote:
>>
>> As always, you can get the latest beta version from the "develop" git 
>> branch. Alternatively, the self-contained source tarball is at 
>> http://www.sagemath.org/download-latest.html 
>>
>> 10ed24e3ed (trac/develop, tag: 9.1.rc0) Updated SageMath version to 
>> 9.1.rc0
>>
>
> If you are testing on macOS, I recommend to merge #29404 and #29408
>
which missed the 9.1.rc0 bus and fix critical failures observed in 
> 9.1.beta9.
>

Can you say how to merge #29404 and #29408
on top of 9.1.rc0 to get things to work in macOS?

I am on macOS 10.14.6 and I have not been able
to build a single version of Sage after 9.0.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/c1680db4-0fc1-4004-86e5-de309894eb9c%40googlegroups.com.


Re: [sage-release] Sage 9.1.rc0 released

2020-04-14 Thread Harald Schilly
well, I don't know anything about how these upstream spkgs are
uploaded, but I have access to the server. I created a symlink from
sage_brial to brial. That should help!

On Tue, Apr 14, 2020 at 3:19 PM Dima Pasechnik  wrote:
>
> On Tue, Apr 14, 2020 at 9:13 PM Harald Schilly  wrote:
> >
> > I tried to build 9.1.rc0 clean from git sources, but it fails at brial
> >
> > it tries to get e.g.
> > http://ftp.leg.uct.ac.za/pub/packages/sage/spkg/upstream/sage_brial/brial-1.2.5.tar.bz2
>
> get the upstream brial tarball, i.e.
> http://ftp.leg.uct.ac.za/pub/packages/sage/spkg/upstream/brial/brial-1.2.5.tar.bz2
> and put it in upstream/
>
> sage_brial and brial are built from the same tarball, but URLs are
> different on mirrors, and one of them
> is broken.
>
> If you know how to fix it, please do.
> (it's the same story as gfortran spkg, which is built from the gcc spkg 
> tarball)
>
>
> > but fails
> >
> > the path I found is
> > http://sage.mirror.garr.it/mirrors/sage/spkg/upstream/brial/...
> > though.
> >
> > the diff is "brial" vs "sage_brial"
> >
> > ... or maybe something is wrong with my repo. git status is clean and
> > HEAD is at 10ed24e3ed0b5440624d5f1a9b18d2f8f89d8126
> >
> > -- harald
> >
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "sage-release" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to sage-release+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-release/CAGG4CB5bh5zCnhQSN4RcxMbT3Zra0bnj6SPTWofB0UPEmad5vA%40mail.gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/CAAWYfq13VtJG%3DTSc%2BhAo8LU1qe-RG_-qf182N1uL%2Bnh7V1VCag%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAGG4CB4vYXYSKj55sD92xGh_yYwzFvuQf08fA0rG-EtwVw%40mail.gmail.com.


Re: [sage-release] Sage 9.1.rc0 released

2020-04-14 Thread Dima Pasechnik
On Tue, Apr 14, 2020 at 9:13 PM Harald Schilly  wrote:
>
> I tried to build 9.1.rc0 clean from git sources, but it fails at brial
>
> it tries to get e.g.
> http://ftp.leg.uct.ac.za/pub/packages/sage/spkg/upstream/sage_brial/brial-1.2.5.tar.bz2

get the upstream brial tarball, i.e.
http://ftp.leg.uct.ac.za/pub/packages/sage/spkg/upstream/brial/brial-1.2.5.tar.bz2
and put it in upstream/

sage_brial and brial are built from the same tarball, but URLs are
different on mirrors, and one of them
is broken.

If you know how to fix it, please do.
(it's the same story as gfortran spkg, which is built from the gcc spkg tarball)


> but fails
>
> the path I found is
> http://sage.mirror.garr.it/mirrors/sage/spkg/upstream/brial/...
> though.
>
> the diff is "brial" vs "sage_brial"
>
> ... or maybe something is wrong with my repo. git status is clean and
> HEAD is at 10ed24e3ed0b5440624d5f1a9b18d2f8f89d8126
>
> -- harald
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/CAGG4CB5bh5zCnhQSN4RcxMbT3Zra0bnj6SPTWofB0UPEmad5vA%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAAWYfq13VtJG%3DTSc%2BhAo8LU1qe-RG_-qf182N1uL%2Bnh7V1VCag%40mail.gmail.com.


Re: [sage-release] Sage 9.1.rc0 released

2020-04-14 Thread Harald Schilly
I tried to build 9.1.rc0 clean from git sources, but it fails at brial

it tries to get e.g.
http://ftp.leg.uct.ac.za/pub/packages/sage/spkg/upstream/sage_brial/brial-1.2.5.tar.bz2
but fails

the path I found is
http://sage.mirror.garr.it/mirrors/sage/spkg/upstream/brial/...
though.

the diff is "brial" vs "sage_brial"

... or maybe something is wrong with my repo. git status is clean and
HEAD is at 10ed24e3ed0b5440624d5f1a9b18d2f8f89d8126

-- harald

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAGG4CB5bh5zCnhQSN4RcxMbT3Zra0bnj6SPTWofB0UPEmad5vA%40mail.gmail.com.