Skip to contentSkip to conversation

Nominating Fengguang Wu - 0-day

Ksummit-discuss Luis R. Rodriguez 12 participants 28 messages Jul 25, 2016 – Aug 1, 2016

lore
Share & tools
lore
#0 lore raw

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up. Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful. If maintainers are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

Luis

#1 lore raw
Quoted 5 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

That's a good point.

Quoted 9 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up. Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful. If maintainers are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

Well, I think it would also help to know how the patch/git tree selection is done. Lately, I've been receiving less reports from 0-day and some issues were found by Arnd's autobuilders after hitting linux-next. I used to get report of compilation breakage 10-15 minutes after the patch submission.

Signature · 3 lines
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#2 lore raw
Quoted 17 lines · Alexandre Belloni
Quoted 5 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

That's a good point.

Quoted 8 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up. Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful. If maintainers are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

I am using it a lot :)

Quoted 5 lines

Well, I think it would also help to know how the patch/git tree selection is done. Lately, I've been receiving less reports from 0-day and some issues were found by Arnd's autobuilders after hitting linux-next. I used to get report of compilation breakage 10-15 minutes after the patch submission.

Pls check if the mailing list is still subscribed. I had the same issue and found that his ID was kicked off from the list, which is quite typical w/ Intel accounts & vger.

Since work is done by scripts, people may not have noticed.

Signature · 1 line
~Vinod
#3 lore raw

Hello,

Quoted 19 lines · On Tuesday 26 Jul 2016 08:40:07 Vinod Koul wrote:
Quoted 17 lines · Alexandre Belloni
Quoted 4 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

That's a good point.

Quoted 9 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up. Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful. If maintainers are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

Quoted 7 lines

I am using it a lot :)

Quoted 5 lines

Well, I think it would also help to know how the patch/git tree selection is done. Lately, I've been receiving less reports from 0-day and some issues were found by Arnd's autobuilders after hitting linux-next. I used to get report of compilation breakage 10-15 minutes after the patch submission.

I second that. 0-day is an amazing tool, but relying on it requires developers to trust that the tool will perform its job as expected. A proper understanding of the logic behind patch/git tree selection would be very valuable, as well as how the build bot handles its 500+ kernel configurations.

Even though 0-day is an external tool, maybe it deserves an entry in Documentation/ ? A public web page hosting the list of all git registered git trees could be useful too.

Quoted 5 lines

Pls check if the mailing list is still subscribed. I had the same issue and found that his ID was kicked off from the list, which is quite typical w/ Intel accounts & vger.

Since work is done by scripts, people may not have noticed.

Signature · 3 lines
Regards,

Laurent Pinchart
#4 lore raw
Quoted 30 lines · Laurent Pinchart

Hello,

Quoted 19 lines · On Tuesday 26 Jul 2016 08:40:07 Vinod Koul wrote:
Quoted 17 lines · Alexandre Belloni
Quoted 4 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

That's a good point.

Quoted 9 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up. Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful. If maintainers are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

Quoted 7 lines

I am using it a lot :)

Quoted 5 lines

Well, I think it would also help to know how the patch/git tree selection is done. Lately, I've been receiving less reports from 0-day and some issues were found by Arnd's autobuilders after hitting linux-next. I used to get report of compilation breakage 10-15 minutes after the patch submission.

Quoted 4 lines

I second that. 0-day is an amazing tool, but relying on it requires developers to trust that the tool will perform its job as expected. A proper understanding of the logic behind patch/git tree selection would be very valuable, as well as how the build bot handles its 500+ kernel configurations.

Agreed, although in his report he does mention the tree used, but would be great if the logic is Documented somewhere.

There seems some basic Documentation up at [1] and [2]

Also the reports can be put on webpage. Last test results of maintainer trees and results of patches run on mailing list. I think that data is available but not present...

Quoted 9 lines

Even though 0-day is an external tool, maybe it deserves an entry in Documentation/ ? A public web page hosting the list of all git registered git trees could be useful too.

Quoted 5 lines

Pls check if the mailing list is still subscribed. I had the same issue and found that his ID was kicked off from the list, which is quite typical w/ Intel accounts & vger.

Since work is done by scripts, people may not have noticed.

[1]: https://01.org/lkp/documentation/0-day-test-service
[2]: https://01.org/lkp/

Signature · 1 line
~Vinod
#5 lore raw
Quoted 31 lines · Vinod Koul
Quoted 30 lines · Laurent Pinchart

Hello,

Quoted 26 lines · On Tuesday 26 Jul 2016 08:40:07 Vinod Koul wrote:
Quoted 17 lines · Alexandre Belloni
Quoted 4 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

That's a good point.

Quoted 9 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up. Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful. If maintainers are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

I am using it a lot :)

Quoted 5 lines

Well, I think it would also help to know how the patch/git tree selection is done. Lately, I've been receiving less reports from 0-day and some issues were found by Arnd's autobuilders after hitting linux-next. I used to get report of compilation breakage 10-15 minutes after the patch submission.

Quoted 7 lines
Quoted 4 lines

I second that. 0-day is an amazing tool, but relying on it requires developers to trust that the tool will perform its job as expected. A proper understanding of the logic behind patch/git tree selection would be very valuable, as well as how the build bot handles its 500+ kernel configurations.

Agreed, although in his report he does mention the tree used, but would be great if the logic is Documented somewhere.

Yeah, sorry the Documentation could be improved.

The 600+ git trees 0-day monitors are tracked here:

https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/tree/repo/linux

Thanks,
Fengguang

#6 lore raw
In reply to Alexandre Belloni
Quoted 19 lines · Alexandre Belloni
Quoted 5 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

That's a good point.

Quoted 9 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up. Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful. If maintainers are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

Quoted 5 lines

Well, I think it would also help to know how the patch/git tree selection is done. Lately, I've been receiving less reports from 0-day and some issues were found by Arnd's autobuilders after hitting linux-next. I used to get report of compilation breakage 10-15 minutes after the patch submission.

Yeah sorry about that! There are many things that can impact 0-day system's stability: regressions, hard disk replacement, proxy issues, mailing list kicking off, vocations, etc. Which should improve over time as we add monitoring and self-test facilities. On the other hand, if you find such issues, please don't hesitate forwarding the error emails to us, so that we can check and take action quickly.

Thanks,
Fengguang

#7 lore raw

Hi Fengguang,

Quoted 24 lines · On Wednesday 27 Jul 2016 22:50:27 Fengguang Wu wrote:
Quoted 17 lines · Alexandre Belloni
Quoted 3 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

That's a good point.

Quoted 9 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up. Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful. If maintainers are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

Quoted 5 lines

Well, I think it would also help to know how the patch/git tree selection is done. Lately, I've been receiving less reports from 0-day and some issues were found by Arnd's autobuilders after hitting linux-next. I used to get report of compilation breakage 10-15 minutes after the patch submission.

Quoted 6 lines

Yeah sorry about that! There are many things that can impact 0-day system's stability: regressions, hard disk replacement, proxy issues, mailing list kicking off, vocations, etc. Which should improve over time as we add monitoring and self-test facilities. On the other hand, if you find such issues, please don't hesitate forwarding the error emails to us, so that we can check and take action quickly.

There's no need to apologize, really. You've done and keep doing an amazing work for which we're all thankful. The biggest problem I see that would stop me from fully relying on 0-day is the lack of information about such downtimes, leading me to wonder if the absence of a report really means that everything is fine. A 0-day status page with information about the current status and the planned downtime, as well as possibly the list of trees covered by 0-day (I don't know whether part of that information could be considered as confidential), would help a lot.

Signature · 3 lines
Regards,

Laurent Pinchart
#8 lore raw

Hi Laurent,

Quoted 34 lines · Laurent Pinchart

Hi Fengguang,

Quoted 24 lines · On Wednesday 27 Jul 2016 22:50:27 Fengguang Wu wrote:
Quoted 17 lines · Alexandre Belloni
Quoted 3 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

That's a good point.

Quoted 9 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up. Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful. If maintainers are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

Quoted 5 lines

Well, I think it would also help to know how the patch/git tree selection is done. Lately, I've been receiving less reports from 0-day and some issues were found by Arnd's autobuilders after hitting linux-next. I used to get report of compilation breakage 10-15 minutes after the patch submission.

Quoted 6 lines

Yeah sorry about that! There are many things that can impact 0-day system's stability: regressions, hard disk replacement, proxy issues, mailing list kicking off, vocations, etc. Which should improve over time as we add monitoring and self-test facilities. On the other hand, if you find such issues, please don't hesitate forwarding the error emails to us, so that we can check and take action quickly.

Quoted 8 lines

There's no need to apologize, really. You've done and keep doing an amazing work for which we're all thankful. The biggest problem I see that would stop me from fully relying on 0-day is the lack of information about such downtimes, leading me to wonder if the absence of a report really means that everything is fine. A 0-day status page with information about the current status and the planned downtime, as well as possibly the list of trees covered by 0-day (I don't know whether part of that information could be considered as confidential), would help a lot.

For that purpose you may subscribe to the BUILD SUCCESS notification by sending me an "opt-in" email with your tree URL.

That notification will be sent 1-2 hours after each branch's git push, which contains the build test progress on that branch. Based on which (or missing of it) you'll know if everything is on the track.

This will actually turn that feature on for your tree:

https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/commit/?id=aa0480dd8d58d234fdf0ff41bcb71a930aa024b9

commit aa0480dd8d58d234fdf0ff41bcb71a930aa024b9

Author:     Fengguang Wu <[email protected]>
Commit:     Fengguang Wu <[email protected]>
CommitDate: Fri Jul 29 04:48:44 2016 +0800

repo: notify build success for pinchartl-fbdev

CC Laurent Pinchart <[email protected]>

---
repo/linux/pinchartl-fbdev | 1 +

1 file changed, 1 insertion(+)
repo/linux/pinchartl-fbdev +0 -0
index bbb4dd1..cc6e19b 100644
@@ -1,5 +1,6 @@

url: git://linuxtv.org/pinchartl/fbdev.git
owner: Laurent Pinchart <[email protected]> +notify_build_success_branch: .*
subsystems:
- drm
- rcar-du

Thanks,
Fengguang

#9 lore raw

Hi Fengguang,

Quoted 43 lines · On Friday 29 Jul 2016 04:53:24 Fengguang Wu wrote:
Quoted 33 lines · Laurent Pinchart
Quoted 25 lines · On Wednesday 27 Jul 2016 22:50:27 Fengguang Wu wrote:
Quoted 18 lines · Alexandre Belloni
Quoted 4 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

That's a good point.

Quoted 9 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up. Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful. If maintainers are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

Quoted 5 lines

Well, I think it would also help to know how the patch/git tree selection is done. Lately, I've been receiving less reports from 0-day and some issues were found by Arnd's autobuilders after hitting linux-next. I used to get report of compilation breakage 10-15 minutes after the patch submission.

Quoted 6 lines

Yeah sorry about that! There are many things that can impact 0-day system's stability: regressions, hard disk replacement, proxy issues, mailing list kicking off, vocations, etc. Which should improve over time as we add monitoring and self-test facilities. On the other hand, if you find such issues, please don't hesitate forwarding the error emails to us, so that we can check and take action quickly.

Quoted 8 lines

There's no need to apologize, really. You've done and keep doing an amazing work for which we're all thankful. The biggest problem I see that would stop me from fully relying on 0-day is the lack of information about such downtimes, leading me to wonder if the absence of a report really means that everything is fine. A 0-day status page with information about the current status and the planned downtime, as well as possibly the list of trees covered by 0-day (I don't know whether part of that information could be considered as confidential), would help a lot.

Quoted 6 lines

For that purpose you may subscribe to the BUILD SUCCESS notification by sending me an "opt-in" email with your tree URL.

That notification will be sent 1-2 hours after each branch's git push, which contains the build test progress on that branch. Based on which (or missing of it) you'll know if everything is on the track.

I know that such a feature exists, but I'm not sure all developers would appreciate the additional e-mail traffic. That's why I proposed a status page that could be polled when needed.

Quoted 23 lines

This will actually turn that feature on for your tree:

https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/commit/?id=aa
0480dd8d58d234fdf0ff41bcb71a930aa024b9

commit aa0480dd8d58d234fdf0ff41bcb71a930aa024b9

Author:     Fengguang Wu <[email protected]>
Commit:     Fengguang Wu <[email protected]>
CommitDate: Fri Jul 29 04:48:44 2016 +0800

repo: notify build success for pinchartl-fbdev

CC Laurent Pinchart <[email protected]>
---
 repo/linux/pinchartl-fbdev | 1 +
 1 file changed, 1 insertion(+)
repo/linux/pinchartl-fbdev +0 -0
index bbb4dd1..cc6e19b 100644

repo/linux/pinchartl-fbdev line 6

Quoted 6 lines
repo/linux/pinchartl-fbdev +1 -0
@@ -1,5 +1,6 @@
 url: git://linuxtv.org/pinchartl/fbdev.git
 owner: Laurent Pinchart <[email protected]>
+notify_build_success_branch: .*
 subsystems:
 - drm
 - rcar-du

Thanks. I will actually deprecate that tree in favour of
git://linuxtv.org/pinchartl/media.git :-) I'll send you a mail when that will be effective.

Signature · 3 lines
Regards,

Laurent Pinchart
#10 lore raw
Quoted 49 lines · Laurent Pinchart

Hi Fengguang,

Quoted 46 lines · On Friday 29 Jul 2016 04:53:24 Fengguang Wu wrote:
Quoted 33 lines · Laurent Pinchart
Quoted 25 lines · On Wednesday 27 Jul 2016 22:50:27 Fengguang Wu wrote:
Quoted 18 lines · Alexandre Belloni
Quoted 4 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

That's a good point.

Quoted 9 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up. Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful. If maintainers are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

Quoted 5 lines

Well, I think it would also help to know how the patch/git tree selection is done. Lately, I've been receiving less reports from 0-day and some issues were found by Arnd's autobuilders after hitting linux-next. I used to get report of compilation breakage 10-15 minutes after the patch submission.

Quoted 6 lines

Yeah sorry about that! There are many things that can impact 0-day system's stability: regressions, hard disk replacement, proxy issues, mailing list kicking off, vocations, etc. Which should improve over time as we add monitoring and self-test facilities. On the other hand, if you find such issues, please don't hesitate forwarding the error emails to us, so that we can check and take action quickly.

Quoted 8 lines

There's no need to apologize, really. You've done and keep doing an amazing work for which we're all thankful. The biggest problem I see that would stop me from fully relying on 0-day is the lack of information about such downtimes, leading me to wonder if the absence of a report really means that everything is fine. A 0-day status page with information about the current status and the planned downtime, as well as possibly the list of trees covered by 0-day (I don't know whether part of that information could be considered as confidential), would help a lot.

For that purpose you may subscribe to the BUILD SUCCESS notification by sending me an "opt-in" email with your tree URL.

Quoted 7 lines
Quoted 3 lines

That notification will be sent 1-2 hours after each branch's git push, which contains the build test progress on that branch. Based on which (or missing of it) you'll know if everything is on the track.

I know that such a feature exists, but I'm not sure all developers would appreciate the additional e-mail traffic. That's why I proposed a status page that could be polled when needed.

I for one really appreciate that I do not need to poll anything and instead I am notified when stuff that I pushed passed/failed some tests. So, even if there are status pages and what's not, please do keep opt-in email notifications.

Thanks Fengguang!

Signature · 1 line
Dmitry
#11 lore raw
Quoted 8 lines · Dmitry Torokhov
Quoted 3 lines

I know that such a feature exists, but I'm not sure all developers would appreciate the additional e-mail traffic. That's why I proposed a status page that could be polled when needed.

I for one really appreciate that I do not need to poll anything and instead I am notified when stuff that I pushed passed/failed some tests. So, even if there are status pages and what's not, please do keep opt-in email notifications.

Same here, I do look for mail from Fengguang after I have pushed stuff up.

Said that, if we have a lookup interface, I won't mind at all, given that sometimes latencies vary, so knowing the latest status, branch and commit built would help.

Also on mailing list tests, I would really like a status page. Right now it only reports errors, which is great. But I won't know if tests were run or not. It happened on one of our lists recently

Quoted 1 line

Thanks Fengguang!

Absolutely, this bot has been a great service to kernel community.

Thanks

Signature · 1 line
~Vinod
#12 lore raw
In reply to Laurent Pinchart
Quoted 49 lines · Laurent Pinchart

Hi Fengguang,

Quoted 46 lines · On Friday 29 Jul 2016 04:53:24 Fengguang Wu wrote:
Quoted 33 lines · Laurent Pinchart
Quoted 25 lines · On Wednesday 27 Jul 2016 22:50:27 Fengguang Wu wrote:
Quoted 18 lines · Alexandre Belloni
Quoted 4 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

That's a good point.

Quoted 9 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up. Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful. If maintainers are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

Quoted 5 lines

Well, I think it would also help to know how the patch/git tree selection is done. Lately, I've been receiving less reports from 0-day and some issues were found by Arnd's autobuilders after hitting linux-next. I used to get report of compilation breakage 10-15 minutes after the patch submission.

Quoted 6 lines

Yeah sorry about that! There are many things that can impact 0-day system's stability: regressions, hard disk replacement, proxy issues, mailing list kicking off, vocations, etc. Which should improve over time as we add monitoring and self-test facilities. On the other hand, if you find such issues, please don't hesitate forwarding the error emails to us, so that we can check and take action quickly.

Quoted 8 lines

There's no need to apologize, really. You've done and keep doing an amazing work for which we're all thankful. The biggest problem I see that would stop me from fully relying on 0-day is the lack of information about such downtimes, leading me to wonder if the absence of a report really means that everything is fine. A 0-day status page with information about the current status and the planned downtime, as well as possibly the list of trees covered by 0-day (I don't know whether part of that information could be considered as confidential), would help a lot.

For that purpose you may subscribe to the BUILD SUCCESS notification by sending me an "opt-in" email with your tree URL.

Quoted 7 lines
Quoted 3 lines

That notification will be sent 1-2 hours after each branch's git push, which contains the build test progress on that branch. Based on which (or missing of it) you'll know if everything is on the track.

I know that such a feature exists, but I'm not sure all developers would appreciate the additional e-mail traffic. That's why I proposed a status page that could be polled when needed.

Such a status web page would be similar to the email notification with no much extra contents, except that it's always there for your polling. If that'd be valuable to you and some few other developers, I'd be glad to push forward the Web UI feature.

I need your understand that there are severe limitations what useful contents we can provide due to the nature of merge-test-bisect. For example, there will be no build logs specific for your branches/commits because the extensive build tests are possible only because your code are tested together with a large number of random others. For the same reason there will be no error/warnings available for browsing before the noisy error/warnings are bisected down. If we expose the unclassified noisy error messages and encourage developers to browse through them and do a guess work "are they likely caused by my commits?", we may be wasting the highly valued developer time.

btw, maybe some maintainers are already informed: 0-day statistics show that ~60% errors can be reported in 2 hours, ~90% errors are reported in 24 hours and there are 1% errors reported after 1 week.

As we extend test coverage aggressively, there are no longer clear moment that we can claim all tests for a branch are complete. The actual build/boot tests may well go on for over a week, covering thousands of kconfigs. The more time consuming functional/performance tests may go on for a month. That's made possible and cost effective thanks to the merge-test-bisect methodology.

So the safe bet is to wait for 1 day's tests before sending out patches. The BUILD SUCCESS notification serves as an indication 0-day robot is not sleeping through. My personal style suggestion would be to stay relaxed, take time and avoid polling. :)

Quoted 18 lines
Quoted 18 lines

This will actually turn that feature on for your tree:

https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/commit/?id=aa
0480dd8d58d234fdf0ff41bcb71a930aa024b9

commit aa0480dd8d58d234fdf0ff41bcb71a930aa024b9

Author:     Fengguang Wu <[email protected]>
Commit:     Fengguang Wu <[email protected]>
CommitDate: Fri Jul 29 04:48:44 2016 +0800

repo: notify build success for pinchartl-fbdev

CC Laurent Pinchart <[email protected]>
---
 repo/linux/pinchartl-fbdev | 1 +
 1 file changed, 1 insertion(+)
Quoted 15 lines

repo/linux/pinchartl-fbdev line 6

Quoted 11 lines
repo/linux/pinchartl-fbdev +1 -0
index bbb4dd1..cc6e19b 100644
@@ -1,5 +1,6 @@
 url: git://linuxtv.org/pinchartl/fbdev.git
 owner: Laurent Pinchart <[email protected]>
+notify_build_success_branch: .*
 subsystems:
 - drm
 - rcar-du

Thanks. I will actually deprecate that tree in favour of
git://linuxtv.org/pinchartl/media.git :-) I'll send you a mail when that will be effective.

OK!

Thanks,
Fengguang

#13 lore raw
Quoted 3 lines · Fengguang Wu

btw, maybe some maintainers are already informed: 0-day statistics show that ~60% errors can be reported in 2 hours, ~90% errors are reported in 24 hours and there are 1% errors reported after 1 week.

If one were to take 0-day code an slap it on some internal big-iron server, and prioritize work for a few developers (say SUSE would do this for its developers) do you expect the turnaround time for reports would be faster if we had bigger-meaner hardware ? These days actually would like to get results back in a few minutes for 90% of errors so wondering how / if others have taken on 0-day internally and made it faster by beefing up the hardware.

Luis

#14 lore raw
Quoted 5 lines · Luis R. Rodriguez
Quoted 3 lines · Fengguang Wu

btw, maybe some maintainers are already informed: 0-day statistics show that ~60% errors can be reported in 2 hours, ~90% errors are reported in 24 hours and there are 1% errors reported after 1 week.

Quoted 7 lines

If one were to take 0-day code an slap it on some internal big-iron server, and prioritize work for a few developers (say SUSE would do this for its developers) do you expect the turnaround time for reports would be faster if we had bigger-meaner hardware ? These days actually would like to get results back in a few minutes for 90% of errors so wondering how / if others have taken on 0-day internally and made it faster by beefing up the hardware.

I'd suspect roughly the same timing given powerful servers but still with reasonable cost considerations.

Intel pretty values the 0-day service and backs it up with 12 parallel build servers, including 4 4S Xeon machines. Since we do merged tests, one may assume most of the servers are working parallel for his code whenever he does a git push. Kernel hackers can feel free to push frequently because the extra pushes are virtually cost free -- the build workers are working cyclicly on latest merged code anyway.

To take free ride of that restless horse, it'd be good to push small topic branches on latest RC kernels, which will have better chances to merge and play well with others code.

Thanks,
Fengguang

#15 lore raw
Quoted 28 lines · Fengguang Wu
Quoted 8 lines · Luis R. Rodriguez
Quoted 4 lines · Fengguang Wu

btw, maybe some maintainers are already informed: 0-day statistics show that ~60% errors can be reported in 2 hours, ~90% errors are reported in 24 hours and there are 1% errors reported after 1 week.

Quoted 7 lines

If one were to take 0-day code an slap it on some internal big-iron server, and prioritize work for a few developers (say SUSE would do this for its developers) do you expect the turnaround time for reports would be faster if we had bigger-meaner hardware ? These days actually would like to get results back in a few minutes for 90% of errors so wondering how / if others have taken on 0-day internally and made it faster by beefing up the hardware.

I'd suspect roughly the same timing given powerful servers but still with reasonable cost considerations.

Intel pretty values the 0-day service and backs it up with 12 parallel build servers, including 4 4S Xeon machines. Since we do merged tests, one may assume most of the servers are working parallel for his code whenever he does a git push. Kernel hackers can feel free to push frequently because the extra pushes are virtually cost free -- the build workers are working cyclicly on latest merged code anyway.

Quoted 3 lines

To take free ride of that restless horse, it'd be good to push small topic branches on latest RC kernels, which will have better chances to merge and play well with others code.

I'm interested in learning more about how this works. I typically base all my topic branches on -rc2 or so, no matter where we are in the cycle, because it makes it easier to rebuild my "next" branch if I discover a problem and want to amend something. But maybe this consumes more 0-day cycles than necessary.

I second the desire for a web page of status. Sometimes things seem to get lost or delayed and I hate to bug Fengguang unnecessarily.

I typically push a topic branch and wait for BUILD_SUCCESS before merging into my "next" branch. I do this manually by watching for the email, but maybe it could be scripted if there were a way to query "build status for SHA-1".

#16 lore raw
In reply to Fengguang Wu
Quoted 14 lines · Fengguang Wu
Quoted 5 lines · Luis R. Rodriguez
Quoted 3 lines · Fengguang Wu

btw, maybe some maintainers are already informed: 0-day statistics show that ~60% errors can be reported in 2 hours, ~90% errors are reported in 24 hours and there are 1% errors reported after 1 week.

Quoted 7 lines

If one were to take 0-day code an slap it on some internal big-iron server, and prioritize work for a few developers (say SUSE would do this for its developers) do you expect the turnaround time for reports would be faster if we had bigger-meaner hardware ? These days actually would like to get results back in a few minutes for 90% of errors so wondering how / if others have taken on 0-day internally and made it faster by beefing up the hardware.

Quoted 2 lines

I'd suspect roughly the same timing given powerful servers but still with reasonable cost considerations.

Interesting, thanks. Let's say I still want to, where is the code?

Quoted 6 lines

Intel pretty values the 0-day service and backs it up with 12 parallel build servers, including 4 4S Xeon machines. Since we do merged tests, one may assume most of the servers are working parallel for his code whenever he does a git push. Kernel hackers can feel free to push frequently because the extra pushes are virtually cost free -- the build workers are working cyclicly on latest merged code anyway.

Awesome thanks! I recently ran into the situation where I may have run into what seems to be a binutils (ld) bug and I want to verify if it is only associated to an odd-ball architecture, I have 2 kconfig entries I know I want tested on all architectures. In the future it may be nice to be able to suggest a given set of kconfig entires one wants as base for all architectures. This may need something like kconfig-sat though [0].

[0] https://kernelnewbies.org/KernelProjects/kconfig-sat

Quoted 3 lines

To take free ride of that restless horse, it'd be good to push small topic branches on latest RC kernels, which will have better chances to merge and play well with others code.

How about linux-next ?

Luis

#17 lore raw
Quoted 27 lines · Luis R. Rodriguez
Quoted 14 lines · Fengguang Wu
Quoted 5 lines · Luis R. Rodriguez
Quoted 3 lines · Fengguang Wu

btw, maybe some maintainers are already informed: 0-day statistics show that ~60% errors can be reported in 2 hours, ~90% errors are reported in 24 hours and there are 1% errors reported after 1 week.

Quoted 7 lines

If one were to take 0-day code an slap it on some internal big-iron server, and prioritize work for a few developers (say SUSE would do this for its developers) do you expect the turnaround time for reports would be faster if we had bigger-meaner hardware ? These days actually would like to get results back in a few minutes for 90% of errors so wondering how / if others have taken on 0-day internally and made it faster by beefing up the hardware.

Quoted 2 lines

I'd suspect roughly the same timing given powerful servers but still with reasonable cost considerations.

Interesting, thanks. Let's say I still want to, where is the code?

Quoted 6 lines

Intel pretty values the 0-day service and backs it up with 12 parallel build servers, including 4 4S Xeon machines. Since we do merged tests, one may assume most of the servers are working parallel for his code whenever he does a git push. Kernel hackers can feel free to push frequently because the extra pushes are virtually cost free -- the build workers are working cyclicly on latest merged code anyway.

Quoted 4 lines

Awesome thanks! I recently ran into the situation where I may have run into what seems to be a binutils (ld) bug and I want to verify if it is only associated to an odd-ball architecture, I have 2 kconfig entries I know I want tested on all architectures. In the future it

If you let me know what those are, I should be able to run them through my build system.

Guenter

Quoted 18 lines

may be nice to be able to suggest a given set of kconfig entires one wants as base for all architectures. This may need something like kconfig-sat though [0].

[0] https://kernelnewbies.org/KernelProjects/kconfig-sat

Quoted 3 lines

To take free ride of that restless horse, it'd be good to push small topic branches on latest RC kernels, which will have better chances to merge and play well with others code.

How about linux-next ?

Luis
_______________________________________________
Ksummit-discuss mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

#18 lore raw
In reply to Luis R. Rodriguez
Quoted 15 lines · Luis R. Rodriguez
Quoted 14 lines · Fengguang Wu
Quoted 12 lines · Luis R. Rodriguez
Quoted 3 lines · Fengguang Wu

btw, maybe some maintainers are already informed: 0-day statistics show that ~60% errors can be reported in 2 hours, ~90% errors are reported in 24 hours and there are 1% errors reported after 1 week.

If one were to take 0-day code an slap it on some internal big-iron server, and prioritize work for a few developers (say SUSE would do this for its developers) do you expect the turnaround time for reports would be faster if we had bigger-meaner hardware ? These days actually would like to get results back in a few minutes for 90% of errors so wondering how / if others have taken on 0-day internally and made it faster by beefing up the hardware.

Quoted 4 lines
Quoted 2 lines

I'd suspect roughly the same timing given powerful servers but still with reasonable cost considerations.

Interesting, thanks. Let's say I still want to, where is the code?

It's not public available. Sorry. I love kernel community and open source, unfortunately it's not a decision can be made by me alone.

Quoted 15 lines
Quoted 6 lines

Intel pretty values the 0-day service and backs it up with 12 parallel build servers, including 4 4S Xeon machines. Since we do merged tests, one may assume most of the servers are working parallel for his code whenever he does a git push. Kernel hackers can feel free to push frequently because the extra pushes are virtually cost free -- the build workers are working cyclicly on latest merged code anyway.

Awesome thanks! I recently ran into the situation where I may have run into what seems to be a binutils (ld) bug and I want to verify if it is only associated to an odd-ball architecture, I have 2 kconfig entries I know I want tested on all architectures. In the future it may be nice to be able to suggest a given set of kconfig entires one wants as base for all architectures. This may need something like kconfig-sat though [0].

Quoted 1 line

[0] https://kernelnewbies.org/KernelProjects/kconfig-sat

I'll reply that in the other email.

Quoted 5 lines
Quoted 3 lines

To take free ride of that restless horse, it'd be good to push small topic branches on latest RC kernels, which will have better chances to merge and play well with others code.

How about linux-next ?

linux-next could be perfectly supported, however in a different "rebase" way than the "merges" for RC kernels.

Suppose there are 100 branches based on -rc2 and another 100 branches on -rc3. We can typically merge most of the 200 branches onto -rc3, since there are relatively few changes between -rc2 and -rc3.

On the other hand, linux-next is a rolling base, it'd be hard to merge next-20160728 itself onto next-20160729, not to mention patches based on them. So if there are 10 branches based on next-20160728 and another 10 branches based on next-20160729, there's little chance to merge test them together. In current situation these linux-next based branches will end up being tested less in 0-day.

We'd like to improve that situation by "rebasing" all linux-next based branches to latest linux-next and test them together. It will make the error reports less faithful to the original commits, however I guess developers working on linux-next more or less accept it as a rolling base and won't care much about the exact linux-next version.

If developers are interested in knowing merge conflicts with others' code, so that he can fix it in advance and get more test coverage in 0-day, we can help auto locate down and report the merge or rebase failures, too. Or build errors due to logical merge conflicts.

Thanks,
Fengguang

#19 lore raw
Quoted 9 lines · Fengguang Wu
Quoted 2 lines

How about linux-next ?

linux-next could be perfectly supported, however in a different "rebase" way than the "merges" for RC kernels.

Suppose there are 100 branches based on -rc2 and another 100 branches on -rc3. We can typically merge most of the 200 branches onto -rc3, since there are relatively few changes between -rc2 and -rc3.

Since linux-next already contains all maintainer branches slated for -next, merging that won't help much and seems tedious. I think 0day should just runs tests on top of linux-next everyday and report, if not done already.

Signature · 1 line
~Vinod
#20 lore raw
Quoted 7 lines · Vinod Koul
Quoted 6 lines · Fengguang Wu
Quoted 2 lines

How about linux-next ?

linux-next could be perfectly supported, however in a different "rebase" way than the "merges" for RC kernels.

Quoted 7 lines
Quoted 3 lines

Suppose there are 100 branches based on -rc2 and another 100 branches on -rc3. We can typically merge most of the 200 branches onto -rc3, since there are relatively few changes between -rc2 and -rc3.

Since linux-next already contains all maintainer branches slated for -next, merging that won't help much and seems tedious. I think 0day should just runs tests on top of linux-next everyday and report, if not done already.

Yes we are already testing linux-next. There are some few trees based on linux-next because many LKML patches could be applied to it for testing -- if they cannot apply to "guessed" maintainer trees and RC kernels. So we have to handle patches on linux-next well.

Thanks,
Fengguang

#21 lore raw
In reply to Fengguang Wu
Quoted 5 lines · Fengguang Wu

I need your understand that there are severe limitations what useful contents we can provide due to the nature of merge-test-bisect. For example, there will be no build logs specific for your branches/commits because the extensive build tests are possible only because your code are tested together with a large number of random others.

I think this'd be an interesting thing to discuss per se, as my personal feeling is that the expectations of maintainers / git tree owners might be slightly diverging from reality.

The reason I am bringing this up is a very recent example here:

	https://lkml.org/lkml/2016/7/28/212

The 0day bot identified my patch as a build-breaker, and it took me quite some time to figure out that this has been actually broken for years already (IOW yes, the treee fails to build with some configs after my patch has been applied, but I'm pretty sure it breaks with the same config even without my patch).

Hence, if you could explain in a little bit more detailed way how developers should interpret the reports, I'd be very grateful for such session.

Special focus should probably be put on regressions -- once reported by your bot, I'd love to know the last-known-good base to compare against.

Oh, and thanks a *lot* for all the 0day efforts, I am pretty sure that it increases the speed of development while maintaining the quality, and a status update from you should IMO always be a welcome KS topic,

Signature · 2 lines
Jiri Kosina
SUSE Labs
#22 lore raw

Hi Jiri,

Quoted 14 lines · Jiri Kosina
Quoted 5 lines · Fengguang Wu

I need your understand that there are severe limitations what useful contents we can provide due to the nature of merge-test-bisect. For example, there will be no build logs specific for your branches/commits because the extensive build tests are possible only because your code are tested together with a large number of random others.

I think this'd be an interesting thing to discuss per se, as my personal feeling is that the expectations of maintainers / git tree owners might be slightly diverging from reality.

The reason I am bringing this up is a very recent example here:

Quoted 7 lines
	https://lkml.org/lkml/2016/7/28/212

The 0day bot identified my patch as a build-breaker, and it took me quite some time to figure out that this has been actually broken for years already (IOW yes, the treee fails to build with some configs after my patch has been applied, but I'm pretty sure it breaks with the same config even without my patch).

Yeah we may be running into an interesting case here: the build error is true and bisect for that build error is correct. The robot end up happily sent report for an innocent patch which happen to trigger a more general problem.

Quoted 6 lines

Hence, if you could explain in a little bit more detailed way how developers should interpret the reports, I'd be very grateful for such session.

Special focus should probably be put on regressions -- once reported by your bot, I'd love to know the last-known-good base to compare against.

In bisect POV, the parent commit builds fine (all the way to vmlinux) -- so it is the last-known-good base. If follow the reproduce steps in the report email, you should be able to confirm that.

The main problem here is, first-bad-commit may not necessarily mean root cause. It'll require human analyzes to reach such a conclusion.

Quoted 3 lines

Oh, and thanks a *lot* for all the 0day efforts, I am pretty sure that it increases the speed of development while maintaining the quality, and a status update from you should IMO always be a welcome KS topic,

Thank you! :)

Regards,
Fengguang

#23 lore raw
In reply to Fengguang Wu
Quoted 27 lines · On Fri, 29 Jul 2016 07:07:13 +0800 Fengguang Wu <[email protected]> wrote:

Such a status web page would be similar to the email notification with no much extra contents, except that it's always there for your polling. If that'd be valuable to you and some few other developers, I'd be glad to push forward the Web UI feature.

I need your understand that there are severe limitations what useful contents we can provide due to the nature of merge-test-bisect. For example, there will be no build logs specific for your branches/commits because the extensive build tests are possible only because your code are tested together with a large number of random others. For the same reason there will be no error/warnings available for browsing before the noisy error/warnings are bisected down. If we expose the unclassified noisy error messages and encourage developers to browse through them and do a guess work "are they likely caused by my commits?", we may be wasting the highly valued developer time.

btw, maybe some maintainers are already informed: 0-day statistics show that ~60% errors can be reported in 2 hours, ~90% errors are reported in 24 hours and there are 1% errors reported after 1 week.

As we extend test coverage aggressively, there are no longer clear moment that we can claim all tests for a branch are complete. The actual build/boot tests may well go on for over a week, covering thousands of kconfigs. The more time consuming functional/performance tests may go on for a month. That's made possible and cost effective thanks to the merge-test-bisect methodology.

Quoted 5 lines

So the safe bet is to wait for 1 day's tests before sending out patches. The BUILD SUCCESS notification serves as an indication 0-day robot is not sleeping through. My personal style suggestion would be to stay relaxed, take time and avoid polling. :)

I'm signed up to the BUILD_SUCCESS notification, but there's been times where they never showed up, probably due to the issues you mentioned. What would be really useful, is just a status page of what commit has been pulled into testing, and if it finished successful or not. It doesn't need to display anything else but where it is in the test.

For example, if there's a web page of my git repo, I could see:

branch ftrace commit SHA1-A - finished failed
branch ftrace commit SHA1-B - finished success
branch ftrace commit SHA1-C - running

Something like that, where I can see that your tests have picked up my lasted push, and if I should be waiting for an email notification or not.

Make sense?

-- Steve

#24 lore raw
Quoted 49 lines · Steven Rostedt
Quoted 27 lines · On Fri, 29 Jul 2016 07:07:13 +0800 Fengguang Wu <[email protected]> wrote:

Such a status web page would be similar to the email notification with no much extra contents, except that it's always there for your polling. If that'd be valuable to you and some few other developers, I'd be glad to push forward the Web UI feature.

I need your understand that there are severe limitations what useful contents we can provide due to the nature of merge-test-bisect. For example, there will be no build logs specific for your branches/commits because the extensive build tests are possible only because your code are tested together with a large number of random others. For the same reason there will be no error/warnings available for browsing before the noisy error/warnings are bisected down. If we expose the unclassified noisy error messages and encourage developers to browse through them and do a guess work "are they likely caused by my commits?", we may be wasting the highly valued developer time.

btw, maybe some maintainers are already informed: 0-day statistics show that ~60% errors can be reported in 2 hours, ~90% errors are reported in 24 hours and there are 1% errors reported after 1 week.

As we extend test coverage aggressively, there are no longer clear moment that we can claim all tests for a branch are complete. The actual build/boot tests may well go on for over a week, covering thousands of kconfigs. The more time consuming functional/performance tests may go on for a month. That's made possible and cost effective thanks to the merge-test-bisect methodology.

Quoted 5 lines

So the safe bet is to wait for 1 day's tests before sending out patches. The BUILD SUCCESS notification serves as an indication 0-day robot is not sleeping through. My personal style suggestion would be to stay relaxed, take time and avoid polling. :)

I'm signed up to the BUILD_SUCCESS notification, but there's been times where they never showed up, probably due to the issues you mentioned. What would be really useful, is just a status page of what commit has been pulled into testing, and if it finished successful or not. It doesn't need to display anything else but where it is in the test.

For example, if there's a web page of my git repo, I could see:

branch ftrace commit SHA1-A - finished failed
branch ftrace commit SHA1-B - finished success
branch ftrace commit SHA1-C - running

Quoted 5 lines

Something like that, where I can see that your tests have picked up my lasted push, and if I should be waiting for an email notification or not.

Make sense?

Yes that makes good sense. A more structured layout could be

trace

├── for-next
│   ├── 97f8827a8c7963756ae7d3ee898675b4667eca73
│   └── HEAD -> 97f8827a8c7963756ae7d3ee898675b4667eca73
└── ftrace
   ├── core
   │   ├── 501c2375253c0795048f48368e0b3e8b2f6646dc
   │   ├── 78aebca2c955c1c5aeb48e12645e13fe3c3461f2
   │   ├── 7fa8b7171a638ad896acabd9a17183b75b70aeb4
   │   ├── 8329e818f14926a6040df86b2668568bde342ebf
   │   ├── de9be5961936523e6cc3a1358b166e4efb42595b
   │   ├── fc54f5a288feb132d089404ef5748725ac669a5c
   │   └── HEAD -> 78aebca2c955c1c5aeb48e12645e13fe3c3461f2
   └── urgent
       ├── 0ded5174e976e2b2a354fe38abf1ebf4492c6dc3
       ├── 90d6c42c7766fe63c724a6ec7758a85b6231b08b
       └── HEAD -> 90d6c42c7766fe63c724a6ec7758a85b6231b08b

Each end node contains log messages showing all the progresses that have been made.

If necessary, symlinks (like HEAD commit's patch-file-name) could be created at top level to make it more convenient to navigate. Such symlinks can be auto deleted after 1 day (when people are less unlikely to look at its status).

Thanks,
Fengguang

#25 lore raw
In reply to Luis R. Rodriguez
Quoted 4 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

Thanks for your appreciations, Luis!

Quoted 3 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up.

I'd be glad to answer questions and more importantly, collect feedbacks on where and how to improve the 0-day infrastructure.

There are 2 major parts in 0-day: build tests and runtime tests. While build tests will be continuously improved, there may be a lot more to be desired for runtime tests, which should be my main focus in the coming year.

Quoted 2 lines

Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful.

Sure if there are interests.

Quoted 5 lines

If maintainers
are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

0-day tries to monitor as many git trees as possible, so that fresh code can be tested before they land maintainer trees and linux-next. To achieve better early code coverage, we periodically check if there are new git trees showing up in git.kernel.org, in mainline git log or mentioned in LKML emails. And add the newly discovered ones unsolicited. :)

That said, it's still possible errors hit linux-next. Sometimes it may be due to bug in 0-day or temporarily out of service. The solution would be to improve 0-day system's stability and add more self-tests to the system. Quick feedbacks about build/boot errors missed by 0-day would also be highly appreciated.

Thanks,
Fengguang

#26 lore raw
Quoted 12 lines · Fengguang Wu
Quoted 4 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

Thanks for your appreciations, Luis!

Quoted 3 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up.

Quoted 8 lines

I'd be glad to answer questions and more importantly, collect feedbacks on where and how to improve the 0-day infrastructure.

There are 2 major parts in 0-day: build tests and runtime tests. While build tests will be continuously improved, there may be a lot more to be desired for runtime tests, which should be my main focus in the coming year.

For runtime test improvements: We should discuss if and how to integrate kasan/syzkaller testing, and/or if it would make sense to set up a separate test bed for that purpose (to avoid overloading 0day).

Thanks,
Guenter

Quoted 30 lines
Quoted 2 lines

Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful.

Sure if there are interests.

Quoted 5 lines

If maintainers
are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

0-day tries to monitor as many git trees as possible, so that fresh code can be tested before they land maintainer trees and linux-next. To achieve better early code coverage, we periodically check if there are new git trees showing up in git.kernel.org, in mainline git log or mentioned in LKML emails. And add the newly discovered ones unsolicited. :)

That said, it's still possible errors hit linux-next. Sometimes it may be due to bug in 0-day or temporarily out of service. The solution would be to improve 0-day system's stability and add more self-tests to the system. Quick feedbacks about build/boot errors missed by 0-day would also be highly appreciated.

Thanks,
Fengguang
_______________________________________________
Ksummit-discuss mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

#27 lore raw
Quoted 16 lines · Guenter Roeck
Quoted 15 lines · Fengguang Wu
Quoted 4 lines · Luis R. Rodriguez

It surprises Fengguang Wu <[email protected]> hasn't been nominated yet, so I'd like to nominate him. The mechanical process should probably include in the future a scrape for top Reported-by contributors.

Thanks for your appreciations, Luis!

Quoted 3 lines

Fengguang's 0-day infrastructure is invaluable to day to day kernel development, having him present would be great for any questions that may come up.

I'd be glad to answer questions and more importantly, collect feedbacks on where and how to improve the 0-day infrastructure.

Quoted 8 lines
Quoted 5 lines

There are 2 major parts in 0-day: build tests and runtime tests. While build tests will be continuously improved, there may be a lot more to be desired for runtime tests, which should be my main focus in the coming year.

For runtime test improvements: We should discuss if and how to integrate kasan/syzkaller testing, and/or if it would make sense to set up a separate test bed for that purpose (to avoid overloading 0day).

I am all for it.
We are attending plumbers, so we will be able to discuss this in person.

Quoted 30 lines
Quoted 30 lines
Quoted 2 lines

Getting a statistical overview / update of impact / any major architectural changes of the 0-day infrastructure would also be very useful.

Sure if there are interests.

Quoted 5 lines

If maintainers
are not yet using 0-day it would be great to hear why. If your contributors are not using 0-day (I know some of you exist) I'd like to know why you don't use it, I often run into issues on linux-next which at times I have to fix, if 0-day would have been used a folowup fix would not have been needed.

0-day tries to monitor as many git trees as possible, so that fresh code can be tested before they land maintainer trees and linux-next. To achieve better early code coverage, we periodically check if there are new git trees showing up in git.kernel.org, in mainline git log or mentioned in LKML emails. And add the newly discovered ones unsolicited. :)

That said, it's still possible errors hit linux-next. Sometimes it may be due to bug in 0-day or temporarily out of service. The solution would be to improve 0-day system's stability and add more self-tests to the system. Quick feedbacks about build/boot errors missed by 0-day would also be highly appreciated.

Thanks,
Fengguang
_______________________________________________
Ksummit-discuss mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss