Difference between revisions of "Online Developer Meeting (2020-10-27)"

From Octave
Jump to navigation Jump to search
m (Correct date.)
(→‎Todays topics: Add notes and memory of Kai)
Line 8: Line 8:
 
=== Octave 6 release status ===
 
=== Octave 6 release status ===
  
* [[6.1 Release Checklist]]
+
{{note|Octave 6 release in November (tentative)}}
** What about {{bug|57591}} "Segmentation faults when running the test suite (mostly with clang)"? (Reported as "blocking" in [[Online_Developer_Meeting_(2020-07-07)|previous dev meeting]], but marked as "dev".)
+
 
* [https://octave.space/savannah/ dynamic bug overview page]
+
* What is left to be done?
 +
** Complete items in [[6.1 Release Checklist]]
 +
** There are '''13''' bugs marked for '''6.0.9x''' release candidates (see [https://octave.space/savannah/ bug overview page])
 +
*** For the Octave 6 release this number has not necessarily to be 0
 +
*** Developers should go through this list and focus on the relevant ones:
 +
**** {{bug|59206}} "crash during matrix multiplication (Win only)"
 +
***** '''Very important''' probably an OpenBLAS issue.
 +
**** {{bug|59331}} "Processor load stays up after `__run_test_suite__`"
 +
***** Still investigating.
 +
**** {{bug|57591}} "Segmentation faults when running the test suite (mostly with clang)"?
 +
***** jwe reported he has a trace log to get to the bottom of it.
 +
 
 +
=== Broken packages in MXE Octave ===
 +
 
 +
* Should there be a grace period for package maintainers to adapt to Octave 6 before the 6.1 release?
 +
** Release is scheduled for November
 +
** Active package maintainers already up-to-date
 +
** Only contact package maintainers who's packages currently fail:
 +
*** [[odepkg]] runs in an infinite loop while testing; BitBucket repo no longer available; Kai contacts cdf via mailing-list
 +
*** [https://octave.sourceforge.io/sparsersb/ SparseRSB] contacted in {{bug|58957}}
 +
* Many broken packages cannot identified in the mxe-builds
 +
** jwe? reported that some packages intentionally deactivate warnings about deprecated functions until it is "too late" and the package no longer builds.  '''Please do not do this.'''
  
 
=== Octave Buildbot (Kai) ===
 
=== Octave Buildbot (Kai) ===
  
 +
* https://octave.space
 +
* Build artifacts are hosted on a private server in Germany ([https://www.ionos.de/server/vps IONOS VPS M], 80 GB SSD, '''No traffic limit''')
 +
** '''Possibility to advertise this page as "Nightly builds"''' (May I do this? 🙂)
 +
* System (1 master, 4 worker) builds once per day the Octave stable branch (if changes happened)
 +
** Octave tarballs (gz, lz, xz)
 +
** Documentation (manual, Doxygen) can be viewed on the site
 +
** All MXE flavors (32, 64, 64-64)
 
* [https://siko1056.github.io/blog/2020/10/16/octave-buildbot-app.html Some article about octave-buildbot].
 
* [https://siko1056.github.io/blog/2020/10/16/octave-buildbot-app.html Some article about octave-buildbot].
* https://octave.space
+
* Source & development: https://github.com/gnu-octave/octave-buildbot
* https://github.com/gnu-octave/octave-buildbot
 
  
 
== Ideas for next meeting ==
 
== Ideas for next meeting ==

Revision as of 20:24, 27 October 2020

Todays topics

  • Meet and greet 5 minutes before meeting (audio testing).

Octave 6 release status

Info icon.svg
Octave 6 release in November (tentative)
  • What is left to be done?
    • Complete items in 6.1 Release Checklist
    • There are 13 bugs marked for 6.0.9x release candidates (see bug overview page)
      • For the Octave 6 release this number has not necessarily to be 0
      • Developers should go through this list and focus on the relevant ones:
        • #59206 "crash during matrix multiplication (Win only)"
          • Very important probably an OpenBLAS issue.
        • #59331 "Processor load stays up after `__run_test_suite__`"
          • Still investigating.
        • #57591 "Segmentation faults when running the test suite (mostly with clang)"?
          • jwe reported he has a trace log to get to the bottom of it.

Broken packages in MXE Octave

  • Should there be a grace period for package maintainers to adapt to Octave 6 before the 6.1 release?
    • Release is scheduled for November
    • Active package maintainers already up-to-date
    • Only contact package maintainers who's packages currently fail:
      • odepkg runs in an infinite loop while testing; BitBucket repo no longer available; Kai contacts cdf via mailing-list
      • SparseRSB contacted in #58957
  • Many broken packages cannot identified in the mxe-builds
    • jwe? reported that some packages intentionally deactivate warnings about deprecated functions until it is "too late" and the package no longer builds. Please do not do this.

Octave Buildbot (Kai)

Ideas for next meeting

Topic suggestions

See also