Re: 6.1rc3 CentOS 7 Build Sweep Report
On Thu, Apr 18, 2024 at 2:00 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hallo Joel, > > it would be nice to have the interrupt get/set priority directives in > RTEMS 6. When do you want to create the RTEMS 6 branch? > Last spring. Seriously, Chris has been cutting 6.1 rc snapshots to help shake out lurking issues. We use tarballs on rtems.org for the RSB and this had to be worked through. rc1 including tools not building at all. rc2 had some issues and I don't recall even getting to building the BSPs. rc3 is looking better. If you have something you want to make 6, I think there is still time. But hopefully very little. We have been working to reduce tickets identifying 6.1 as a milestone for months. --joel > > -- > embedded brains GmbH & Co. KG > Herr Sebastian HUBER > Dornierstr. 4 > 82178 Puchheim > Germany > email: sebastian.hu...@embedded-brains.de > phone: +49-89-18 94 741 - 16 > fax: +49-89-18 94 741 - 08 > > Registergericht: Amtsgericht München > Registernummer: HRB 157899 > Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler > Unsere Datenschutzerklärung finden Sie hier: > https://embedded-brains.de/datenschutzerklaerung/ > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: 6.1rc3 CentOS 7 Build Sweep Report
Hallo Joel, it would be nice to have the interrupt get/set priority directives in RTEMS 6. When do you want to create the RTEMS 6 branch? -- embedded brains GmbH & Co. KG Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 741 - 16 fax: +49-89-18 94 741 - 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/ ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: 6.1rc3 CentOS 7 Build Sweep Report
On 18/4/2024 4:13 am, Joel Sherrill wrote: > Hi > > 6.1rc3 appears to be in pretty good shape on CentOS 7 (w/GCC 8 and Python 3 > SCL). Results should be on the build@ list. One odd issue appears to be in the > rtems-tester. > > Testing a riscv-bsp with spike, I get this output. It is repeated with other > spike/risc-v bsp tests. Any ideas? > > Exception in thread _stdout[spike]: > Traceback (most recent call last): > File "/opt/rh/rh-python36/root/usr/lib64/python3.6/threading.py", line 916, > in > _bootstrap_inner > self.run() > File "/opt/rh/rh-python36/root/usr/lib64/python3.6/threading.py", line 864, > in run > self._target(*self._args, **self._kwargs) > File "/home/joel/rtems-6.1rc3/tools/6/share/rtems/rtemstoolkit/execute.py", > line 226, in _readthread > data = data.decode(sys.stdout.encoding) > UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: > invalid > start byte The rtems-tools's execute.py needs to be updated to use an incremental decoder codec. This also happened in the RSB and was fixed with: https://git.rtems.org/rtems-source-builder/commit/source-builder/sb/execute.py?id=e04c84191b790b7bddd179bc67337e4205b61f8e Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: 6.1rc3 CentOS 7 Build Sweep Report
UTF-8 start byte cannot be 0xff. Off-by-1 bug is possible. Maybe a hidden control character is throwing off the count but being stripped away prior to the attempt to convert to UTF-8. On Apr 17, 2024, at 1:13 PM, Joel Sherrill wrote: Hi 6.1rc3 appears to be in pretty good shape on CentOS 7 (w/GCC 8 and Python 3 SCL). Results should be on the build@ list. One odd issue appears to be in the rtems-tester. Testing a riscv-bsp with spike, I get this output. It is repeated with other spike/risc-v bsp tests. Any ideas? Exception in thread _stdout[spike]: Traceback (most recent call last): File "/opt/rh/rh-python36/root/usr/lib64/python3.6/threading.py", line 916, in _bootstrap_inner self.run() File "/opt/rh/rh-python36/root/usr/lib64/python3.6/threading.py", line 864, in run self._target(*self._args, **self._kwargs) File "/home/joel/rtems-6.1rc3/tools/6/share/rtems/rtemstoolkit/execute.py", line 226, in _readthread data = data.decode(sys.stdout.encoding) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
6.1rc3 CentOS 7 Build Sweep Report
Hi 6.1rc3 appears to be in pretty good shape on CentOS 7 (w/GCC 8 and Python 3 SCL). Results should be on the build@ list. One odd issue appears to be in the rtems-tester. Testing a riscv-bsp with spike, I get this output. It is repeated with other spike/risc-v bsp tests. Any ideas? Exception in thread _stdout[spike]: Traceback (most recent call last): File "/opt/rh/rh-python36/root/usr/lib64/python3.6/threading.py", line 916, in _bootstrap_inner self.run() File "/opt/rh/rh-python36/root/usr/lib64/python3.6/threading.py", line 864, in run self._target(*self._args, **self._kwargs) File "/home/joel/rtems-6.1rc3/tools/6/share/rtems/rtemstoolkit/execute.py", line 226, in _readthread data = data.decode(sys.stdout.encoding) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte RTEMS Testing - Tester, 6.0.not_released [ 3/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 L:0 i:0 W:0 | riscv64/rv64imac: cdtest.exe ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
