From: "Pavel Machek" <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Cc: kernel-build-reports@lists.linaro.org, kernelci-results@groups.io
Subject: Re: [cip-dev] cip/linux-4.4.y-cip usb: 4 runs, 2 regressions (v4.4.243-cip51-21-g1d9a9094c010)
Date: Fri, 4 Dec 2020 17:40:08 +0100 [thread overview]
Message-ID: <20201204164008.GB1781@duo.ucw.cz> (raw)
In-Reply-To: <5fc87876.1c69fb81.a7e0a.0844@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1864 bytes --]
Hello, bot. Can you speak english?
> cip/linux-4.4.y-cip usb: 4 runs, 2 regressions (v4.4.243-cip51-21-g1d9a9094c010)
>
>
> * usb.compare-freeze: https://kernelci.org/test/case/id/5fc871ebf573faf8a4c94cca
> new failure (last pass: v4.4.243-cip51-10-gd7466739b72e9)
>
> 2020-12-03 05:04:20.932000+00:00 + /usr/sbin/rtcwake -d rtc0 -m freeze -s 1
> 2020-12-03 05:04:20.932000+00:00 rtcwake: assuming RTC uses UTC ...
> 2020-12-03 05:04:20.937000+00:00 rtcwake: wakeup from \"freeze\" using rtc0 at Thu Dec 3 05:04:23 2020
> 2020-12-03 05:04:20.954000+00:00 [ 18.787404] PM: Syncing filesystems ... done.
> 2020-12-03 05:04:20.967000+00:00 [ 18.792542] Freezing user space processes ... (elapsed 0.001 seconds) done.
> 2020-12-03 05:04:20.968000+00:00 [ 18.800704] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
> 2020-12-03 05:04:20.972000+00:00 [ 18.809224] Suspending console(s) (use no_console_suspend to debug)
> 2020-12-03 05:04:23.674000+00:00 [ 18.865290] hub 3-1:1.0: activate --> -113
> 2020-12-03 05:04:23.675000+00:00 [ 18.867538] PM: suspend of devices complete after 51.550 msecs
> 2020-12-03 05:04:23.685000+00:00 [ 18.868293] PM: late suspend of devices complete after 0.750 msecs
> ... (66 line(s) more)
I'm not sure where you see failure here, plus I find it hard to
believe that we have broken anything between
v4.4.243-cip51-10-gd7466739b72e9 and v4.4.243-cip51-21-g1d9a9094c010.
Can you elaborate what is wrong, and maybe re-run tests with
v4.4.243-cip51-10-gd7466739b72e9 to see if this is maybe some kind of
random failure?
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5943): https://lists.cip-project.org/g/cip-dev/message/5943
Mute This Topic: https://lists.cip-project.org/mt/78682105/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-12-04 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 5:32 [cip-dev] cip/linux-4.4.y-cip usb: 4 runs, 2 regressions (v4.4.243-cip51-21-g1d9a9094c010) kernelci.org bot
2020-12-04 16:40 ` Pavel Machek [this message]
2020-12-04 17:17 ` Chris Paterson
2020-12-04 17:48 ` Pavel Machek
2020-12-07 9:02 ` Guillaume Tucker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201204164008.GB1781@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).