Thomas Huth writes:
> On 17/01/2023 11.44, Daniel P. Berrangé wrote:
> ...
>> And what i think is test float being overly verbose
>>>> Testing f16_le_quiet
>>46464 tests total.
>> 1
>> 2
>> 3
>> 4
>>46464 tests performed.
>> Could be written as
>>
On 17/01/2023 11.44, Daniel P. Berrangé wrote:
...
And what i think is test float being overly verbose
>> Testing f16_le_quiet
46464 tests total.
1
2
3
4
46464 tests performed.
Could be written as
>> Testing f16_le_quiet: 46464 tests total
On Wed, Jan 18, 2023 at 01:55:49PM +0100, Thomas Huth wrote:
> On 17/01/2023 11.44, Daniel P. Berrangé wrote:
> > On Tue, Jan 17, 2023 at 11:32:42AM +0100, Thomas Huth wrote:
> ...
> > > - Instead of doing "cat meson-logs/testlog.txt" in the CI
> > >scripts, we switch to "tail -n 1000 meson-log
On 17/01/2023 11.44, Daniel P. Berrangé wrote:
On Tue, Jan 17, 2023 at 11:32:42AM +0100, Thomas Huth wrote:
...
- Instead of doing "cat meson-logs/testlog.txt" in the CI
scripts, we switch to "tail -n 1000 meson-logs/testlog.txt"
instead
Tail requires that it has consumed the entire doc
On Tue, 17 Jan 2023 at 12:02, Daniel P. Berrangé wrote:
>
> On Tue, Jan 17, 2023 at 11:16:32AM +, Peter Maydell wrote:
> > On Tue, 17 Jan 2023 at 10:44, Daniel P. Berrangé
> > wrote:
> > > Something random that looks like bad text data
> > >
> > > ▶ 166/619 /ptimer/oneshot
> > > policy=no_i
On Tue, Jan 17, 2023 at 12:22:35PM +, Peter Maydell wrote:
> On Tue, 17 Jan 2023 at 12:02, Daniel P. Berrangé wrote:
> >
> > On Tue, Jan 17, 2023 at 11:16:32AM +, Peter Maydell wrote:
> > > On Tue, 17 Jan 2023 at 10:44, Daniel P. Berrangé
> > > wrote:
> > > > Something random that looks
On Tue, Jan 17, 2023 at 11:16:32AM +, Peter Maydell wrote:
> On Tue, 17 Jan 2023 at 10:44, Daniel P. Berrangé wrote:
> > Something random that looks like bad text data
> >
> > ▶ 166/619 /ptimer/oneshot
> > policy=no_immediate_...
On Tue, 17 Jan 2023 at 10:44, Daniel P. Berrangé wrote:
> Something random that looks like bad text data
>
> ▶ 166/619 /ptimer/oneshot
> policy=no_immediate_...snip�
I don't understand this one. The string comes from
On Tue, Jan 17, 2023 at 11:32:42AM +0100, Thomas Huth wrote:
> On 17/01/2023 11.23, Peter Maydell wrote:
> > On Mon, 16 Jan 2023 at 16:55, Peter Maydell
> > wrote:
> > >
> > > On Thu, 15 Dec 2022 at 15:30, Thomas Huth wrote:
> > > >
> > > > We're still running into the problem that some logs a
On 17/01/2023 11.23, Peter Maydell wrote:
On Mon, 16 Jan 2023 at 16:55, Peter Maydell wrote:
On Thu, 15 Dec 2022 at 15:30, Thomas Huth wrote:
We're still running into the problem that some logs are cut in the
gitlab-CI since they got too big. The biggest part of the log is
still the output
On Mon, 16 Jan 2023 at 16:55, Peter Maydell wrote:
>
> On Thu, 15 Dec 2022 at 15:30, Thomas Huth wrote:
> >
> > We're still running into the problem that some logs are cut in the
> > gitlab-CI since they got too big. The biggest part of the log is
> > still the output of the qom-test. Let's stop
On Thu, 15 Dec 2022 at 15:30, Thomas Huth wrote:
>
> We're still running into the problem that some logs are cut in the
> gitlab-CI since they got too big. The biggest part of the log is
> still the output of the qom-test. Let's stop printing the properties
> by default to get to a saner size here
On 15/12/22 16:30, Thomas Huth wrote:
We're still running into the problem that some logs are cut in the
gitlab-CI since they got too big. The biggest part of the log is
still the output of the qom-test. Let's stop printing the properties
by default to get to a saner size here. The full output ca
We're still running into the problem that some logs are cut in the
gitlab-CI since they got too big. The biggest part of the log is
still the output of the qom-test. Let's stop printing the properties
by default to get to a saner size here. The full output can still
be enabled by setting V=2 (or hi
14 matches
Mail list logo
