[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #59869] [octave forge] (parallel) tests trigge
From: |
Christian Ehrhardt |
Subject: |
[Octave-bug-tracker] [bug #59869] [octave forge] (parallel) tests trigger "int32 scalar cannot be indexed with" on systems with 1 CPU |
Date: |
Thu, 14 Jan 2021 14:46:36 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.141 Safari/537.36 |
Follow-up Comment #7, bug #59869 (project octave):
> I can't reproduce it, so I depend on you doing debugging.
I can try to help as long as there are clear instructions what I can do. But
really - to reproduce just use a single-cpu system (or if you have no KVM or
cloud to do so, just reboot with maxcpus=1 - that does the same.
> Since their are containers involved, some notes:
No containers involved, those were just listed as not reproducing environments
initially. KVM guests are the easiest, just give them only one vCPU and you
have a reproducing environment.
> - configure, make, and running must happen in the same environment with
respect to system- and octave- libraries.
All packages built with the same build dependencies in Debian/Ubuntu. And
since they built close to each other those where mostly identical.
> - I don't know if container systems can trick exec() ...
As I said, if you read in detail no container(magic) needed. Just 1 CPU and
this should reproduce
> Further notes:
>
> You can look if the spawned octave processes result from the same Octave
binary as the spawning process.
I can look what binary spawns (when I have more time = tomorrow). But what
exactly do you want me to check or report there? Do you want me to verify if
spawning&spawned processes are all from the same binary?
> The Octave release was changed from 6.1 to 'other' -- at what release did
the issue happen?
As I outlined in the report 6.1.1 is right and octave-parallel 4.0 - not sure
what/who/what changed the release - but it was not intentional.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?59869>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #59869] octave-parallel tests trigger "int32 scalar cannot be indexed with" on systems with 1 CPU, Christian Ehrhardt, 2021/01/14
- [Octave-bug-tracker] [bug #59869] [octave forge] (parallel) tests trigger "int32 scalar cannot be indexed with" on systems with 1 CPU, Markus Mützel, 2021/01/14
- [Octave-bug-tracker] [bug #59869] [octave forge] (parallel) tests trigger "int32 scalar cannot be indexed with" on systems with 1 CPU, Christian Ehrhardt, 2021/01/14
- [Octave-bug-tracker] [bug #59869] [octave forge] (parallel) tests trigger "int32 scalar cannot be indexed with" on systems with 1 CPU, Christian Ehrhardt, 2021/01/14
- [Octave-bug-tracker] [bug #59869] [octave forge] (parallel) tests trigger "int32 scalar cannot be indexed with" on systems with 1 CPU, Markus Mützel, 2021/01/14
- [Octave-bug-tracker] [bug #59869] [octave forge] (parallel) tests trigger "int32 scalar cannot be indexed with" on systems with 1 CPU, Markus Mützel, 2021/01/14
- [Octave-bug-tracker] [bug #59869] [octave forge] (parallel) tests trigger "int32 scalar cannot be indexed with" on systems with 1 CPU, Olaf Till, 2021/01/14
- [Octave-bug-tracker] [bug #59869] [octave forge] (parallel) tests trigger "int32 scalar cannot be indexed with" on systems with 1 CPU,
Christian Ehrhardt <=
- [Octave-bug-tracker] [bug #59869] [octave forge] (parallel) tests trigger "int32 scalar cannot be indexed with" on systems with 1 CPU, Markus Mützel, 2021/01/15
- [Octave-bug-tracker] [bug #59869] [octave forge] (parallel) tests trigger "int32 scalar cannot be indexed with" on systems with 1 CPU, Olaf Till, 2021/01/15