Oh, nice. Thanks for the feedback.
On 1/29/19 1:39 PM, Martin Simmons wrote:
Thanks, all of those warnings are gone from the latest git build.
__Martin
On Fri, 25 Jan 2019 16:20:37 +0100, Kern Sibbald said:
Hello,
I am *finally* back from a month on the west coast of the US, followed
by 4 days at the Bacula Systems bi-annual meeting and am working on
these problems. It is strange that I don't find them here, but as
always, I *much* appreciate Martin's patches.
I have also updated regress.bacula.org to use Branch-9.4 rather than
Branch-9.0, so hopefully things will start to work. That said, I cannot
find the output listing of even the jobs that I run (all are successful).
In any, case, please keep the patches when appropriate coming, I will
apply them, and Dan, please do keep running your cdash regressions.
Best regards,
Kern
On 1/24/19 7:43 PM, Martin Simmons wrote:
On Thu, 24 Jan 2019 10:54:06 -0500, Dan Langille said:
On Jan 24, 2019, at 10:39 AM, Martin Simmons <mar...@lispworks.com> wrote:
On Wed, 23 Jan 2019 18:04:30 -0500, Dan Langille said:
The full test run is at
https://gist.github.com/dlangille/f9b32caf723ce96576cb74ac038f64a2
You need to find the logs of the failing tests (possibly in a file called
test.out).
It seem to be: Restored files differ
I added test.out to the above mentioned gist.
This doesn't contain the actual differences unfortunately.
Check that REGRESS_DEBUG=1 in the environment when running the tests (e.g. in
regress/nightly-disk).
If that doesn't show more, I suggest grepping the whole output tree for
short-incremental-test to see if there are more detailed log files.
__Martin
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
