Hi Jose,
On Fri, Feb 09, 2018 at 01:58:48PM -0800, Jose Luis Rivero wrote:
>
> I've been in contact with upstream and seems like it is a flaky test so
> they recommend me to disable it since it highly depend on time. I did that:
>
>
On 08/02/18 05:25, Andreas Tille wrote:
>
> I can confirm that the problem is somehow randomized. I tried the
> following patch which sometimes helps for non-reproducable issues
>
> $ git diff
> diff --git a/debian/rules b/debian/rules
> index 6b7ed6a..e677071 100755
> --- a/debian/rules
> +++
Hi Jose,
On Wed, Feb 07, 2018 at 03:33:00PM -0800, Jose Luis Rivero wrote:
> I was not able to reproduce the problem with gbp using the --pbuilder
> option. Our buildfarm that only runs docker (not pbuilder) also did not
> catch it. I've modified the rules file to run tests on an writable HOME
>
I was not able to reproduce the problem with gbp using the --pbuilder
option. Our buildfarm that only runs docker (not pbuilder) also did not
catch it. I've modified the rules file to run tests on an writable HOME
directory:
Hi Jose,
I had a sponsor look at ignition-common but when building in a pbuilder
chroot I've got:
...
#7: UNIT_Console_TEST ...***Timeout 240.00 sec
[==] Running 17 tests from 1 test case.
[--] Global test environment set-up.
[--] 17 tests from
5 matches
Mail list logo
