I ran
date ; make check UPDATE=1 ; date
last night, starting at 23:04.
It is still running. Twelve hours seems like a long time.
So I did:
grep '^\*\*\*\*\* KVM PLUTO RUNNING test' tests.LOG10 | sort | uniq -c
| sort -n
31 lines were unique.
256 appeared twice.
Why the heck are
On Sun, 14 Jun 2015, D. Hugh Redelmeier wrote:
So I did:
grep '^\*\*\*\*\* KVM PLUTO RUNNING test' tests.LOG10 | sort | uniq -c
| sort -n
31 lines were unique.
256 appeared twice.
Why the heck are tests being run twice? When will it stop?
Because you crossed the date line at midnigh
| From: Paul Wouters
| On Sun, 14 Jun 2015, D. Hugh Redelmeier wrote:
|
| > 31 lines were unique.
| > 256 appeared twice.
| >
| > Why the heck are tests being run twice? When will it stop?
|
| Because you crossed the date line at midnight ?
That would be a dumb reason, but a reason. It doesn
On Sun, 14 Jun 2015, D. Hugh Redelmeier wrote:
| > Is there a better command for me to use?
|
| I use: cd testing/pluto ; find . -name OUTPUT | xargs rm -rf ;
| ../utils/swantest
|
| I'm not sure if it suffers the same problem.
It doesn't do a clean build.
I do that manually beforehand.
It
| From: Paul Wouters
| > | I use: cd testing/pluto ; find . -name OUTPUT | xargs rm -rf ;
| > | ../utils/swantest
| > It doesn't do tests in the defined order.
| >
| > It doesn't respect TESTLIST except by accident.
|
| Yes it does?
Sorry, I misread. I thought that the swantest was being driv
| From: D. Hugh Redelmeier
| 31 lines were unique.
| 256 appeared twice.
By the time it finished, there were only 11 test run exactly once.
The rest were run exactly twice.
___
Swan-dev mailing list
Swan-dev@lists.libreswan.org
https://lists.libreswan.
On Sun, 14 Jun 2015, D. Hugh Redelmeier wrote:
I went over your results and they are good. Please push the code.
One interesting thing about the run is that somehow all the refhim=
entries went back to 0. Which is what they used to be, but then
for some reason most turned to 1. I'm not sure whic
On Sun, Jun 14, 2015 at 11:38:32AM -0400, D. Hugh Redelmeier wrote:
> | From: Paul Wouters
>
> | On Sun, 14 Jun 2015, D. Hugh Redelmeier wrote:
> |
> | > 31 lines were unique.
> | > 256 appeared twice.
> | >
> | > Why the heck are tests being run twice? When will it stop?
> |
> | Because you c
On Sun, 14 Jun 2015, Antony Antony wrote:
| > Why the heck are tests being run twice? When will it stop?
|
| Because you crossed the date line at midnight ?
If it is make check crossing the midnight should not be a problem. It was fixed
a long time ago. I would love to see a proof of this h
| From: Paul Wouters
| On Sun, 14 Jun 2015, D. Hugh Redelmeier wrote:
| I went over your results and they are good. Please push the code.
OK. Working on that now.
___
Swan-dev mailing list
Swan-dev@lists.libreswan.org
https://lists.libreswan.org/mailm
| From: D. Hugh Redelmeier
| Why the heck are tests being run twice? When will it stop?
I ran the tests this morning. Started at 1:29 local time; ended at 8:35.
Each test that was run was run only once.
I wonder what was different.
___
Swan-dev ma
I suspect that the algorithm is something like:
for try in 1..5:
for test in tests:
archive = form-archive-directory-from test + date + git + ...
if no archive or not archive passed
delete OUTPUT
run test
copy OUTPUT to archive
So failing tests are alw
On Tue, Jun 16, 2015 at 04:38:59PM -0400, Andrew Cagney wrote:
> I suspect that the algorithm is something like:
may be small difference. directory is set outside the loop.
runoutput = archive-dir/ + "%Y-%m-%d" + nodename + "make showversion"
for try in 1..5:
for test in tests:
if no r
On 16 June 2015 at 19:51, Antony Antony wrote:
> On Tue, Jun 16, 2015 at 04:38:59PM -0400, Andrew Cagney wrote:
>> I suspect that the algorithm is something like:
>
> may be small difference. directory is set outside the loop.
>
> runoutput = archive-dir/ + "%Y-%m-%d" + nodename + "make showversi
14 matches
Mail list logo
