pharo

pharo copied to clipboard

[CI] Segmentation faults on code loading

2

We are seeing now (sind 17/10) Segmentation faults on full image build. Here is an example where it happens with newtools, but a prior run it crashed on loading spec....

MarcusDenker

Completion is showing stuff with a dot now?

1

while defining a class for my tests I got the following completion result. 

Ducasse

Simplify progress bar theme management

1

The theme management of the progress bar is a little messy because it gives a progress bar parameter that is never used. And some methods have "style" in the name...

jecisc

Take into account new lines when navigating through text word-by-word. We considered many different cases, check all tests. We got inspiration from: textmate vs code several browser-based text editors They...

guillep

Interval size error with Floating Point step

1

Pharo v9 through v12 overstates the size of (-4 to: 4 by: 0.1) **Bug description** Since 0.1 is not exactly represented in FP, we should see only 80 elements in...

rjsargent

Indistinguishable `SortedCollection`s often considered not-equal due to sortBlock

3

**Bug description** SortedCollection includes its `sortBlock` as part of equality comparison. This is reasonable enough—worth noting that the two sortBlocks have to result in the same sort order or the...

daniels220

experimental: Inline caches for the interpreter

1

Leaves "free slots" after method selectors. This is a simple, backwards-compatible change. The design of bytecode ICs is not yet written on stone. The current VM implementation stores the `(selector,...

iglosiggio

[CI] test timeout WIN SocketStreamTest

3

On the new win CI, we have these test timing on: [Windows64.Network.Tests.SocketStreamTest.testUpToAfterCloseNonSignaling](https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/PR-17241/1/testReport/junit/Windows64.Network.Tests/SocketStreamTest/windows_64___Tests_windows_64___testUpToAfterCloseNonSignaling/) [windows-64 / Tests-windows-64 / Windows64.Network.Tests.SocketStreamTest.testUpToAfterCloseSignaling](https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/PR-17241/1/testReport/junit/Windows64.Network.Tests/SocketStreamTest/windows_64___Tests_windows_64___testUpToAfterCloseSignaling/) [windows-64 / Tests-windows-64 / Windows64.Network.Tests.SocketStreamTest.testUpToAllAfterCloseNonSignaling](https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/PR-17241/1/testReport/junit/Windows64.Network.Tests/SocketStreamTest/windows_64___Tests_windows_64___testUpToAllAfterCloseNonSignaling/) [windows-64 / Tests-windows-64 / Windows64.Network.Tests.SocketStreamTest.testUpToAllAfterCloseSignaling](https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/PR-17241/1/testReport/junit/Windows64.Network.Tests/SocketStreamTest/windows_64___Tests_windows_64___testUpToAllAfterCloseSignaling/)

MarcusDenker

Updated https://github.com/pharo-project/pharo/pull/16277/files Fixes #15507 Fixes #15169

hernanmd

When you want to run code coverage, you select test packages and packageS that these tests test. Now you can only select one package so this defeats the point.

Ducasse