Conversation
|
We're still having segmentation faults with 2.7.1 |
e14b5f9 to
9af27a3
Compare
9af27a3 to
fe44044
Compare
|
I've just re-run 2 cancelled and 1 failing job |
|
meetings tests succeeded but "proposals (system public)" crashed with Segmentation Fault again. "Proposals (system admin)" hanged again I've run the tests locally twice and I'm not having the seg fault. I'll run the whole proposals test suite locally. I'm on Ubuntu 18.04. |
|
@tramuntanal I ran |
|
Yes it's an |
|
I reran one job because it got hanging (Proposals system admin ran for 6h). @tramuntanal did you encounter any segfaults after downgrading the |
|
Hi @mrcasals yes I also re-ran the workflow twice yesterday because it was hanging forever... Now it finished with a segmentation fault again, but now in maybe we can rollback #6513 or push the upgrade to rails 6 which will require some work and delay the release of 0.23 (any other idea?). We'll comment it internally with @decidim/product |
|
By the way, I've been trying to upgrade to Rails 6 just to see what happens, and bundler doesn't finish the |
|
@oriolgual Yesterday I tried to upgrade to |
|
I managed to update all the dependencies @tramuntanal! |
|
Unrelated, but has a strategy to capture deprecation warnings that we usually don't realize we have, and might help on upgrading: https://github.blog/2020-08-25-upgrading-github-to-ruby-2-7/ |
|
tests are failing due to a previous error in "create test app" step: I've scheduled some time today to also push on this PR |
|
It turns out that, as Segmentation Faults airse randomly, all tests succeeded by casuality. After merging #6524 into |
|
Closing since this was more of a test. |
|
Oh, no! @tramuntanal are you planning on working on this? It would be awesome if we could upgrade to Rails 6, since Rails 6.1 is about to be released! |
|
@mrcasals We tried to push this PR a little bit more but got stuck with webpack configuration. There's no plan to keep working on this right now. |
|
@tramuntanal isn't the |
|
Yes @mrcasals , |
|
I've restored the branch so we/someone can keep the work and dig around it. Can you describe the issues you were having @tramuntanal? 😄 |
🎩 What? Why?
Upgrade to the latest Ruby version available. Other than using the latest stable version this is also to try to see if all the segmentation faults we get in GitHub Actions are solved using this version.