Open jemelyah opened 10 months ago
For JRuby implementation we need to add it to matrix, I wouldn't merge just one bit of the process I believe it's much harder than this. Can you add it to matrix?
@route
Can you add it to matrix?
Sorry, I missed the reference. Do you mean their communications channel on Matrix?
Oh I meant to https://github.com/rubycdp/ferrum/blob/main/.github/workflows/tests.yml Let's see how it's failing on CI
Oh I meant to https://github.com/rubycdp/ferrum/blob/main/.github/workflows/tests.yml Let's see how it's failing on CI
@route I have added jruby
to the tests.yml, but it seems it needs approval to run.
Looks like at some point connection to browser crashes and then after that all tests failing
@jemelyah could you please rebase against latest main branch?
@route just pushed the merged changes
@route would you mind taking a look at the current PR, if it is ok, then I'll try to handle the original issue described here: Issue 402
On it
@route I've updated the code to reflect latest changes in Process class; however, my local tests are still failing, so I'll need to figure out how to handle the problems.
Added JRuby to the matrix once again, lost it somewhere.
@route I was finally able to get the tests going locally, by redirecting the process output to the buffered reader instead of a file. Is it possible to run the test suite once again on the matrix?
@jemelyah how long does it take to tests to pass locally?
I cannot test it on windows but I cannot even install gems on jruby 9.4.5.0 (3.1.4) 2023-11-02 1abae2700f Java HotSpot(TM) 64-Bit Server VM 19.0.1+10-21 on 19.0.1+10-21 +jit [arm64-darwin] on my mac. It's failing.
@route, sorry for the delay; we are solving some issues with our solution to this; I hope to update this PR when we are done.
@route, unfortunately, it fails and hangs with Exception handling servers: #<IOError: closed stream>
in the test environment for jruby-9.4. Locally, the tests pass, so I'll try to replicate and investigate the closed stream issue.
This looks very familiar to me, as I faced it long ago https://github.com/rubycdp/ferrum/issues/15 It works much slower in github actions.
References https://github.com/rubycdp/ferrum/issues/400.
For the JRuby implementations, use Java ProcessBuilder to redirect Chrome process output to a specific file instead of stdout.