** Description changed:

- Due to formatting errors, the nosetest autopkgtest prevents 26.10.2 from
- migrating.
+ [ Impact ]
+ 
+ Due to formatting errors, the nosetest autopkgtest prevents 26.04.21 and 
26.10.2 from migrating.
+ This is not impacting users directly, as this is only pycodetest verification 
failing, but this impacts development, as failing autopkgtest can hide other 
more critical issues.
+ 
+ [ Test Plan ]
+ 
+ Autopkgtest should be green, on both Stonking and Resolute.
+ 
+ [ Where problems could occur ]
+ 
+ Fixing pycodestyle's problem could yield some other syntax errors that 
weren't there before, breaking u-r-u.
+ This SRU comes along with a bunch of other bugs that also have there own test 
plans which should exercise the part of the code that is changed, so I don't 
believe there is much risk here.
+ 
+ [ Other Info ]
+ 
+ The following bug is what triggered the code change in the first place:
+ https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2150319
+ 
+ Other unrelated bug that is also part of that SRU:
+ https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2151216

** Description changed:

  [ Impact ]
  
  Due to formatting errors, the nosetest autopkgtest prevents 26.04.21 and 
26.10.2 from migrating.
  This is not impacting users directly, as this is only pycodetest verification 
failing, but this impacts development, as failing autopkgtest can hide other 
more critical issues.
  
  [ Test Plan ]
  
  Autopkgtest should be green, on both Stonking and Resolute.
  
  [ Where problems could occur ]
  
  Fixing pycodestyle's problem could yield some other syntax errors that 
weren't there before, breaking u-r-u.
- This SRU comes along with a bunch of other bugs that also have there own test 
plans which should exercise the part of the code that is changed, so I don't 
believe there is much risk here.
+ This SRU comes along with a bunch of other bugs that also have there own test 
plans which should exercise the part of the code that is changed, so I don't 
believe there is too much risk here.
  
  [ Other Info ]
  
  The following bug is what triggered the code change in the first place:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2150319
  
  Other unrelated bug that is also part of that SRU:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2151216

** Description changed:

  [ Impact ]
  
  Due to formatting errors, the nosetest autopkgtest prevents 26.04.21 and 
26.10.2 from migrating.
  This is not impacting users directly, as this is only pycodetest verification 
failing, but this impacts development, as failing autopkgtest can hide other 
more critical issues.
  
  [ Test Plan ]
  
  Autopkgtest should be green, on both Stonking and Resolute.
  
  [ Where problems could occur ]
  
  Fixing pycodestyle's problem could yield some other syntax errors that 
weren't there before, breaking u-r-u.
- This SRU comes along with a bunch of other bugs that also have there own test 
plans which should exercise the part of the code that is changed, so I don't 
believe there is too much risk here.
+ This SRU comes along with a bunch of other bugs that also have there own test 
plans which should exercise the part of the code that is changed, so I don't 
believe there is too much risk here if the other bugs are verified successfully.
  
  [ Other Info ]
  
  The following bug is what triggered the code change in the first place:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2150319
  
  Other unrelated bug that is also part of that SRU:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2151216

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2154724

Title:
  26.04.21 and 26.10.2 autopkgtest failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2154724/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to