I'm not entirely happy with the regression potential section, so let me
work a bit on that.
"Hopefully not much" is not a valid regression potential analysis as it
gives us, the SRU team, no insight into what the actual situation is
like. We all have wishful thinking about our changes! This section
requires looking and understanding the code changes, looking at which
parts of the code are modified and doing a though exercise: hmmm, if
this code is changed, what other parts can it affect? Where should we
expect any problems appear, just in case?
Only then we, as the SRU team, can make a decision whether it is safe
enough to go forward with the SRU or not. Also, it gives everyone a
better understanding what additional dogfooding we might want to perform
to minimize regression risk. Lastly, it's also makes easier bisecting
whenever some regression is found later, when trying to identify which
change is responsible.
Another thing that I'm not entirely happy with is the lack of any DEP-3
headers on any of the patches in the actual uploads. Because of that I
don't know where the patches come from, have those been upstreamed?
I will gladly re-visit those once these issues are resolved.
** Changed in: skiboot (Ubuntu Groovy)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904585
Title:
opal-prd: Have a worker process handle page offlining (Fixes
"PlatServices: dyndealloc memory_error() failed" is getting reported
in error log (opal-prd))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
