Re: Build failed in Jenkins: osv-build-nightly #1451

2018-04-29 Thread Waldek Kozaczuk
By the way I also send a patch that based on my tests also fixes tcp-nbwrite On Sun, Apr 29, 2018 at 9:31 AM, Waldek Kozaczuk wrote: > See my responses below. > > On Sunday, April 29, 2018 at 6:56:10 AM UTC-4, Nadav Har'El wrote: >> >> >> On Fri, Apr 27, 2018 at 5:41 PM, Waldek Kozaczuk >> wrot

Re: Build failed in Jenkins: osv-build-nightly #1451

2018-04-29 Thread Waldek Kozaczuk
See my responses below. On Sunday, April 29, 2018 at 6:56:10 AM UTC-4, Nadav Har'El wrote: > > > On Fri, Apr 27, 2018 at 5:41 PM, Waldek Kozaczuk > wrote: > >> This time tst-unordered-ring-mpsc failed (line 60). >> > > What do you mean "this time"? In the message you quote below, the error > is

Re: Build failed in Jenkins: osv-build-nightly #1451

2018-04-29 Thread Nadav Har'El
On Fri, Apr 27, 2018 at 6:19 PM, Waldek Kozaczuk wrote: > My theory might be right. > > I ran simple experiment by adding this before first assert > in test_when_ring_gets_full test: > sched::thread::pin(sched::cpus[0]); > > and then before assert(!ring.push(5)); > sched::thread::pin(sched::cpus[

Re: Build failed in Jenkins: osv-build-nightly #1451

2018-04-29 Thread Nadav Har'El
On Fri, Apr 27, 2018 at 5:41 PM, Waldek Kozaczuk wrote: > This time tst-unordered-ring-mpsc failed (line 60). > What do you mean "this time"? In the message you quote below, the error is, "as usual", in tst-tcp-nbwrite.so. Or do you mean that you ran tests on your own machine, and saw a failure

Re: Build failed in Jenkins: osv-build-nightly #1451

2018-04-27 Thread Waldek Kozaczuk
My theory might be right. I ran simple experiment by adding this before first assert in test_when_ring_gets_full test: sched::thread::pin(sched::cpus[0]); and then before assert(!ring.push(5)); sched::thread::pin(sched::cpus[1]); I received this error: OSv v0.24-519-g2a7a27b eth0: 192.168.122

Re: Build failed in Jenkins: osv-build-nightly #1451

2018-04-27 Thread Waldek Kozaczuk
This time tst-unordered-ring-mpsc failed (line 60). I briefly looked at it and it seems to me that the test makes an assumption that it will be executed on the same CPU. The unordered_ring_mpsc structure holds vector for each cpu. But what if the thread running the test get migrated to differen

Build failed in Jenkins: osv-build-nightly #1451

2018-04-23 Thread jenkins
See Changes: [geraldonetto] add encrypt (3) functions (fix #945) [geraldonetto] add crypt (3) tests -- [...truncated 149.75 KB...] Adding /tests/tst-excep