| 2020-09-16 18:22:18 |
Bryce Harrington |
bug |
|
|
added bug |
| 2020-09-16 18:22:24 |
Bryce Harrington |
php-parser (Ubuntu): importance |
Undecided |
High |
|
| 2020-09-16 18:22:29 |
Bryce Harrington |
php-parser (Ubuntu): status |
New |
Triaged |
|
| 2020-09-16 18:22:33 |
Bryce Harrington |
php-parser (Ubuntu): assignee |
|
Bryce Harrington (bryce) |
|
| 2020-09-16 18:22:40 |
Bryce Harrington |
tags |
|
server-next |
|
| 2020-09-16 18:22:51 |
Bryce Harrington |
summary |
Integer parsing failure on armhf blocks autopkgtests on focal |
[SRU] Integer parsing failure on armhf blocks autopkgtests on focal |
|
| 2020-09-16 18:23:24 |
Bryce Harrington |
description |
php-parser's autopkgtest has been failing in focal on armhf for some time:
http://autopkgtest.ubuntu.com/packages/p/php-parser/focal/armhf
The test failure is due to an integer format mismatch. We spotted this issue on groovy and flagged it for upstream:
https://github.com/nikic/PHP-Parser/issues/662
There doesn't appear to be a fix identified yet, so we addressed it in groovy by disabling the faulty test. That is likely the least-risk fix for focal, too. |
php-parser's autopkgtest has been failing in focal on armhf for some time:
http://autopkgtest.ubuntu.com/packages/p/php-parser/focal/armhf
The test failure is due to an integer format mismatch. We spotted this issue on groovy and flagged it for upstream:
https://github.com/nikic/PHP-Parser/issues/662
There doesn't appear to be a fix identified yet, so we addressed it in groovy by disabling the faulty test. That is likely the least-risk fix for focal, too.
https://launchpad.net/ubuntu/+source/php-parser/4.4.0-1ubuntu2 |
|
| 2020-09-16 18:25:16 |
Bryce Harrington |
description |
php-parser's autopkgtest has been failing in focal on armhf for some time:
http://autopkgtest.ubuntu.com/packages/p/php-parser/focal/armhf
The test failure is due to an integer format mismatch. We spotted this issue on groovy and flagged it for upstream:
https://github.com/nikic/PHP-Parser/issues/662
There doesn't appear to be a fix identified yet, so we addressed it in groovy by disabling the faulty test. That is likely the least-risk fix for focal, too.
https://launchpad.net/ubuntu/+source/php-parser/4.4.0-1ubuntu2 |
php-parser's autopkgtest has been failing in focal on armhf for some time:
http://autopkgtest.ubuntu.com/packages/p/php-parser/focal/armhf
The test failure is due to an integer format mismatch. We spotted this issue on groovy and flagged it for upstream:
https://github.com/nikic/PHP-Parser/issues/662
There doesn't appear to be a fix identified yet. We addressed it in groovy by disabling the faulty test, and that may be a low-risk way to address it for focal, too.
https://launchpad.net/ubuntu/+source/php-parser/4.4.0-1ubuntu2 |
|
| 2020-09-29 22:51:09 |
Bryce Harrington |
description |
php-parser's autopkgtest has been failing in focal on armhf for some time:
http://autopkgtest.ubuntu.com/packages/p/php-parser/focal/armhf
The test failure is due to an integer format mismatch. We spotted this issue on groovy and flagged it for upstream:
https://github.com/nikic/PHP-Parser/issues/662
There doesn't appear to be a fix identified yet. We addressed it in groovy by disabling the faulty test, and that may be a low-risk way to address it for focal, too.
https://launchpad.net/ubuntu/+source/php-parser/4.4.0-1ubuntu2 |
[Impact]
Other php SRUs end up blocked from migration due to a test case in php-parser that fails due to an integer format mismatch.
[Test Case]
1. Create lxc container for ubuntu-focal
2. Install php-parser
3. Run autopkgtest php-parser -- null
The testsuite should pass but it does not, and fails with this error:
TBD
[Regression Potential]
Since this is a testsuite fix for integer parsing on armhf, the two things to watch for would be a) issues relating to the testsuite, or b) issues particular to armhf (especially traceable to integer parsing behavior). However, in the first case, the testsuite's behavior would crop up only during building / migrating in the archive and would not produce user-visible effects. In the second case, integer parsing issues already exist in released code so would not be a true regression, the test case only exposes them - by preventing other php packages from migrating.
[Discussion]
php-parser's autopkgtest has been failing in focal on armhf for some time:
http://autopkgtest.ubuntu.com/packages/p/php-parser/focal/armhf
The test failure is due to an integer format mismatch. We spotted this issue on groovy and flagged it for upstream:
https://github.com/nikic/PHP-Parser/issues/662
There doesn't appear to be a fix identified yet. We addressed it in groovy by disabling the faulty test, and that may be a low-risk way to address it for focal, too.
https://launchpad.net/ubuntu/+source/php-parser/4.4.0-1ubuntu2 |
|
| 2020-09-29 22:51:56 |
Bryce Harrington |
nominated for series |
|
Ubuntu Groovy |
|
| 2020-09-29 22:51:56 |
Bryce Harrington |
bug task added |
|
php-parser (Ubuntu Groovy) |
|
| 2020-09-29 22:51:56 |
Bryce Harrington |
nominated for series |
|
Ubuntu Focal |
|
| 2020-09-29 22:51:56 |
Bryce Harrington |
bug task added |
|
php-parser (Ubuntu Focal) |
|
| 2020-09-29 22:52:02 |
Bryce Harrington |
php-parser (Ubuntu Focal): assignee |
|
Bryce Harrington (bryce) |
|
| 2020-09-29 22:52:04 |
Bryce Harrington |
php-parser (Ubuntu Focal): importance |
Undecided |
High |
|
| 2020-09-29 22:52:07 |
Bryce Harrington |
php-parser (Ubuntu Focal): status |
New |
Triaged |
|
| 2020-09-29 22:52:10 |
Bryce Harrington |
php-parser (Ubuntu Groovy): status |
Triaged |
Fix Released |
|
| 2020-09-29 23:13:53 |
Bryce Harrington |
description |
[Impact]
Other php SRUs end up blocked from migration due to a test case in php-parser that fails due to an integer format mismatch.
[Test Case]
1. Create lxc container for ubuntu-focal
2. Install php-parser
3. Run autopkgtest php-parser -- null
The testsuite should pass but it does not, and fails with this error:
TBD
[Regression Potential]
Since this is a testsuite fix for integer parsing on armhf, the two things to watch for would be a) issues relating to the testsuite, or b) issues particular to armhf (especially traceable to integer parsing behavior). However, in the first case, the testsuite's behavior would crop up only during building / migrating in the archive and would not produce user-visible effects. In the second case, integer parsing issues already exist in released code so would not be a true regression, the test case only exposes them - by preventing other php packages from migrating.
[Discussion]
php-parser's autopkgtest has been failing in focal on armhf for some time:
http://autopkgtest.ubuntu.com/packages/p/php-parser/focal/armhf
The test failure is due to an integer format mismatch. We spotted this issue on groovy and flagged it for upstream:
https://github.com/nikic/PHP-Parser/issues/662
There doesn't appear to be a fix identified yet. We addressed it in groovy by disabling the faulty test, and that may be a low-risk way to address it for focal, too.
https://launchpad.net/ubuntu/+source/php-parser/4.4.0-1ubuntu2 |
[Impact]
Other php SRUs end up blocked from migration due to a test case in php-parser that fails due to an integer format mismatch.
[Test Case]
1. Create lxc container for ubuntu-focal
2. Install php-parser
3. Run autopkgtest php-parser -- null
The testsuite should pass but it does not, and fails with several invalid token lexer cases starting with and similar to this one:
1) PhpParser\CodeParsingTest::testParse with data set "tmp/autopkgtest.eZ6NuZ/build.Ar8/src/test/code/parser/errorHandling/lexerErrors.test#1" ('Lexer errors (/tmp/autopkgtes....test)', Binary String: 0x3c3f7068700a0...032343b, Binary String: 0x556e657870656...0290a29, null)
RangeException: The lexer returned an invalid token (id=320, value=)
/usr/share/php/PhpParser/ParserAbstract.php:216
/usr/share/php/PhpParser/ParserAbstract.php:158
/tmp/autopkgtest.eZ6NuZ/build.Ar8/src/test/PhpParser/CodeParsingTest.php:58
/tmp/autopkgtest.eZ6NuZ/build.Ar8/src/test/PhpParser/CodeParsingTest.php:21
[Regression Potential]
Since this is a testsuite fix for integer parsing on armhf, the two things to watch for would be a) issues relating to the testsuite, or b) issues particular to armhf (especially traceable to integer parsing behavior). However, in the first case, the testsuite's behavior would crop up only during building / migrating in the archive and would not produce user-visible effects. In the second case, integer parsing issues already exist in released code so would not be a true regression, the test case only exposes them - by preventing other php packages from migrating.
[Discussion]
php-parser's autopkgtest has been failing in focal on armhf for some time:
http://autopkgtest.ubuntu.com/packages/p/php-parser/focal/armhf
The test failure is due to an integer format mismatch. We spotted this issue on groovy and flagged it for upstream:
https://github.com/nikic/PHP-Parser/issues/662
There doesn't appear to be a fix identified yet. We addressed it in groovy by disabling the faulty tests (the one listed in this bug, and the one in LP: #1878102), and that may be a low-risk way to address it for focal, too.
https://launchpad.net/ubuntu/+source/php-parser/4.4.0-1ubuntu2 |
|
| 2020-10-14 00:06:16 |
Bryce Harrington |
description |
[Impact]
Other php SRUs end up blocked from migration due to a test case in php-parser that fails due to an integer format mismatch.
[Test Case]
1. Create lxc container for ubuntu-focal
2. Install php-parser
3. Run autopkgtest php-parser -- null
The testsuite should pass but it does not, and fails with several invalid token lexer cases starting with and similar to this one:
1) PhpParser\CodeParsingTest::testParse with data set "tmp/autopkgtest.eZ6NuZ/build.Ar8/src/test/code/parser/errorHandling/lexerErrors.test#1" ('Lexer errors (/tmp/autopkgtes....test)', Binary String: 0x3c3f7068700a0...032343b, Binary String: 0x556e657870656...0290a29, null)
RangeException: The lexer returned an invalid token (id=320, value=)
/usr/share/php/PhpParser/ParserAbstract.php:216
/usr/share/php/PhpParser/ParserAbstract.php:158
/tmp/autopkgtest.eZ6NuZ/build.Ar8/src/test/PhpParser/CodeParsingTest.php:58
/tmp/autopkgtest.eZ6NuZ/build.Ar8/src/test/PhpParser/CodeParsingTest.php:21
[Regression Potential]
Since this is a testsuite fix for integer parsing on armhf, the two things to watch for would be a) issues relating to the testsuite, or b) issues particular to armhf (especially traceable to integer parsing behavior). However, in the first case, the testsuite's behavior would crop up only during building / migrating in the archive and would not produce user-visible effects. In the second case, integer parsing issues already exist in released code so would not be a true regression, the test case only exposes them - by preventing other php packages from migrating.
[Discussion]
php-parser's autopkgtest has been failing in focal on armhf for some time:
http://autopkgtest.ubuntu.com/packages/p/php-parser/focal/armhf
The test failure is due to an integer format mismatch. We spotted this issue on groovy and flagged it for upstream:
https://github.com/nikic/PHP-Parser/issues/662
There doesn't appear to be a fix identified yet. We addressed it in groovy by disabling the faulty tests (the one listed in this bug, and the one in LP: #1878102), and that may be a low-risk way to address it for focal, too.
https://launchpad.net/ubuntu/+source/php-parser/4.4.0-1ubuntu2 |
[Impact]
Other PHP SRUs are being blocked due to test failures in php-parser. The test case failures appear to be due to irregularities with integer parsing particular to the test framework rather than identifying actual bugs.
[Test Case]
1. Create lxc container for ubuntu-focal
2. Install php-parser
3. Run autopkgtest php-parser -- null
The testsuite should pass but it does not, and fails with several invalid token lexer cases starting with and similar to this one:
1) PhpParser\CodeParsingTest::testParse with data set "tmp/autopkgtest.eZ6NuZ/build.Ar8/src/test/code/parser/errorHandling/lexerErrors.test#1" ('Lexer errors (/tmp/autopkgtes....test)', Binary String: 0x3c3f7068700a0...032343b, Binary String: 0x556e657870656...0290a29, null)
RangeException: The lexer returned an invalid token (id=320, value=)
/usr/share/php/PhpParser/ParserAbstract.php:216
/usr/share/php/PhpParser/ParserAbstract.php:158
/tmp/autopkgtest.eZ6NuZ/build.Ar8/src/test/PhpParser/CodeParsingTest.php:58
/tmp/autopkgtest.eZ6NuZ/build.Ar8/src/test/PhpParser/CodeParsingTest.php:21
The build system also runs the test suite, so an alternative way to reproduce the failure is to do a package build of php-parser in lxc.
[Regression Potential]
Since this is a testsuite fix for integer parsing, the two things to watch for would be a) issues relating to the testsuite, or b) issues particular to integer parsing behavior. However, in the first case, the testsuite's behavior would crop up only during building / migrating in the archive and would not produce user-visible effects. In the second case, integer parsing issues already exist in released code so would not be a true regression, the test case only exposes them - by preventing other php packages from migrating.
[Discussion]
php-parser's autopkgtest has been failing in focal on armhf for some time:
http://autopkgtest.ubuntu.com/packages/p/php-parser/focal/armhf
The test failure is due to an integer format mismatch. We spotted this issue on groovy and flagged it for upstream:
https://github.com/nikic/PHP-Parser/issues/662
There doesn't appear to be a fix identified yet. We addressed it in groovy by disabling the faulty tests (the one listed in this bug, and the one in LP: #1878102), and that may be a low-risk way to address it for focal, too.
https://launchpad.net/ubuntu/+source/php-parser/4.4.0-1ubuntu2 |
|
| 2020-10-14 00:24:14 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~bryce/ubuntu/+source/php-parser/+git/php-parser/+merge/392194 |
|
| 2020-10-28 15:30:35 |
Robie Basak |
tags |
server-next |
block-proposed-focal server-next |
|
| 2020-10-28 15:31:33 |
Robie Basak |
php-parser (Ubuntu Focal): status |
Triaged |
Fix Committed |
|
| 2020-10-28 15:31:35 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-10-28 15:31:36 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2020-10-28 15:31:38 |
Robie Basak |
tags |
block-proposed-focal server-next |
block-proposed-focal server-next verification-needed verification-needed-focal |
|
| 2020-10-29 17:44:46 |
Bryce Harrington |
tags |
block-proposed-focal server-next verification-needed verification-needed-focal |
block-proposed-focal server-next verification-done verification-done-focal |
|
| 2020-10-29 17:44:54 |
Bryce Harrington |
php-parser (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
