All of lore.kernel.org
 help / color / mirror / Atom feed
* what to do with a private BUILD REGRESSION report ?
@ 2021-08-09 16:11 jim.cromie
  2021-09-02  6:16 ` Chen, Rong A
  0 siblings, 1 reply; 2+ messages in thread
From: jim.cromie @ 2021-08-09 16:11 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]

I recently (3 hrs ago) got a report from lkp

[jimc:dd-drm-next] BUILD REGRESSION 72004a480e5609bb441794ac5e75fc2aa95ca500

Why is this a private email, and not sent to kbuild-all too ?
It seems counter to convention,
and all my other brown-bag errors are splayed out for ridicule ;-)

and more importantly...
why is it different than the more public reports ?
did this revision get further than previous ones ? 
what milestone did it reach ?


As to its contents

Error/Warning in current branch:

drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_debug.c:63:54: error: expected ')' before string constant
lib/dynamic_debug.c:1227:52: error: invalid use of undefined type 'struct module'

possible Error/Warning in current branch:

drivers/gpu/drm/drm_print.c:62:52: error: expected ')' before string constant
lib/dynamic_debug.c:1227:52: error: incomplete definition of type 'struct module'

it looks like a proper compile err,
why is it reported this way, and not like others Ive received (this from 8/5)
[kbuild-all] [jimc:dd-drm-next 7/8] drivers/gpu/drm/drm_print.c:64:41: error: expected ')' before string constant
those others include triggering .config, and cross compile script

is the difference that the error is on 8/8, after I shuffled patch order ?

lkp ran the patchset on a lot of configs,
are these configs available for download ?
If they are, could you add a link to the report ?

thanks,
Jim

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: what to do with a private BUILD REGRESSION report ?
  2021-08-09 16:11 what to do with a private BUILD REGRESSION report ? jim.cromie
@ 2021-09-02  6:16 ` Chen, Rong A
  0 siblings, 0 replies; 2+ messages in thread
From: Chen, Rong A @ 2021-09-02  6:16 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 2247 bytes --]

Hi Jim,

Sorry for the late.

On 8/10/2021 12:11 AM, jim.cromie(a)gmail.com wrote:
> I recently (3 hrs ago) got a report from lkp
> 
> [jimc:dd-drm-next] BUILD REGRESSION 72004a480e5609bb441794ac5e75fc2aa95ca500
> 
> Why is this a private email, and not sent to kbuild-all too ?
> It seems counter to convention,
> and all my other brown-bag errors are splayed out for ridicule ;-)
> 
> and more importantly...
> why is it different than the more public reports ?
> did this revision get further than previous ones ?
> what milestone did it reach ?


kbuild-all mailing list is used to archive the build reports,
BUILD REGRESSION is a summary report for the author or owner.

> 
> 
> As to its contents
> 
> Error/Warning in current branch:
> 
> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_debug.c:63:54: error: expected ')' before string constant
> lib/dynamic_debug.c:1227:52: error: invalid use of undefined type 'struct module'
> 
> possible Error/Warning in current branch:
> 
> drivers/gpu/drm/drm_print.c:62:52: error: expected ')' before string constant
> lib/dynamic_debug.c:1227:52: error: incomplete definition of type 'struct module'
> 
> it looks like a proper compile err,
> why is it reported this way, and not like others Ive received (this from 8/5)

we limited the report number for the same commit to avoid too many noise.

> [kbuild-all] [jimc:dd-drm-next 7/8] drivers/gpu/drm/drm_print.c:64:41: error: expected ')' before string constant
> those others include triggering .config, and cross compile script
> 
> is the difference that the error is on 8/8, after I shuffled patch order ?

it should be not related to the patch order.

> 
> lkp ran the patchset on a lot of configs,
> are these configs available for download ?
> If they are, could you add a link to the report ?

we only attach the config on the build report, there's many configs 
mentioned in this BUILD REGRESSION report, we don't have a link to 
download all of them.

Best Regards,
Rong Chen

> 
> thanks,
> Jim
> _______________________________________________
> kbuild-all mailing list -- kbuild-all(a)lists.01.org
> To unsubscribe send an email to kbuild-all-leave(a)lists.01.org
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-09-02  6:16 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-09 16:11 what to do with a private BUILD REGRESSION report ? jim.cromie
2021-09-02  6:16 ` Chen, Rong A

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.