Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ipp-2.1.test fails on mips #4576

Closed
michaelrsweet opened this issue Feb 11, 2015 · 6 comments
Closed

ipp-2.1.test fails on mips #4576

michaelrsweet opened this issue Feb 11, 2015 · 6 comments
Labels
priority-low
Milestone
Stable

Comments

@michaelrsweet
Copy link
Collaborator

Version: 2.0.3
CUPS.org User: odyx

Hi Michael,

After the upload of CUPS 2.0.2 to Debian (experimental), I've noticed the reappearance of a MIPS test suite failure that we had introduced with the patch for STR: #2913 that we had added in 1.7.5. Dropping the patch fixed the test failure, but this test failure appeared back on 2.0.2 (that is the only 2.x version we built) without patches.

In short:

That said, I couldn't pin-point what makes MIPS the only architecture (and we have a large panel: https://buildd.debian.org/status/package.php?p=cups&suite=experimental ) for which the ipp-2.1.test fails.

Cheers,

OdyX

[0] http://anonscm.debian.org/cgit/printing/cups.git/tree/debian/patches/str2913-limit-Get-Jobs-replies-to-500-jobs.patch?id=f8314812c11ca657290d900b6c76868bbafa3602
@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

I need the test results file (HTML report) that is produced from the failed "make check" to diagnose this further...

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

Fixed in Subversion repository.

Was able to reproduce sporadically on one of my VMs finally; looks like a timing issue in the IPP/1.1 test file.

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: odyx

Hi Michael,

This FTBFS continued to appear on later versions of CUPS.

Here are the build failures of 2.0.2 with the patch you provided (2.0.2-3 on Debian):

And here are the ones of 2.0.3 without said patch (already applied):

I've now re-built CUPS on a Debian mips porterbox, and am attaching the HTML build log to this message. The problematic part is probably:

RFC 2911 section 3.2.6: Get-Jobs Operation (which-jobs, requested-at [FAIL]
    RECEIVED: 496 bytes in response
    status-code = successful-ok (successful-ok)
    EXPECTED: job-name
    EXPECTED: time-at-processing

Thanks in advance, cheers,

OdyX

2 similar comments
@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: odyx

Hi Michael,

This FTBFS continued to appear on later versions of CUPS.

Here are the build failures of 2.0.2 with the patch you provided (2.0.2-3 on Debian):

And here are the ones of 2.0.3 without said patch (already applied):

I've now re-built CUPS on a Debian mips porterbox, and am attaching the HTML build log to this message. The problematic part is probably:

RFC 2911 section 3.2.6: Get-Jobs Operation (which-jobs, requested-at [FAIL]
    RECEIVED: 496 bytes in response
    status-code = successful-ok (successful-ok)
    EXPECTED: job-name
    EXPECTED: time-at-processing

Thanks in advance, cheers,

OdyX

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: odyx

Hi Michael,

This FTBFS continued to appear on later versions of CUPS.

Here are the build failures of 2.0.2 with the patch you provided (2.0.2-3 on Debian):

And here are the ones of 2.0.3 without said patch (already applied):

I've now re-built CUPS on a Debian mips porterbox, and am attaching the HTML build log to this message. The problematic part is probably:

RFC 2911 section 3.2.6: Get-Jobs Operation (which-jobs, requested-at [FAIL]
    RECEIVED: 496 bytes in response
    status-code = successful-ok (successful-ok)
    EXPECTED: job-name
    EXPECTED: time-at-processing

Thanks in advance, cheers,

OdyX

@michaelrsweet
Copy link
Collaborator Author

"str4576.patch":

Index: test/ipp-1.1.test

--- test/ipp-1.1.test (revision 12660)
+++ test/ipp-1.1.test (working copy)
@@ -3,7 +3,7 @@

IPP/1.1 test suite.

-# Copyright 2007-2013 by Apple Inc.
+# Copyright 2007-2015 by Apple Inc.

Copyright 2001-2006 by Easy Software Products. All rights reserved.

These coded instructions, statements, and computer programs are the

@@ -429,22 +429,22 @@
ATTR keyword requested-attributes all

STATUS successful-ok
  • EXPECT job-id OF-TYPE integer IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >0
  • EXPECT job-uri OF-TYPE uri IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE "$IPP_URI_SCHEME"
  • EXPECT job-printer-uri OF-TYPE uri IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE "$IPP_URI_SCHEME"
  • EXPECT ?job-id OF-TYPE integer IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >0
  • EXPECT ?job-uri OF-TYPE uri IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE "$IPP_URI_SCHEME"
  • EXPECT ?job-printer-uri OF-TYPE uri IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE "$IPP_URI_SCHEME"
    EXPECT ?job-more-info OF-TYPE uri IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE "$HTTP_URI_SCHEME"
  • EXPECT job-name OF-TYPE name IN-GROUP job-attributes-tag COUNT 1
  • EXPECT job-originating-user-name OF-TYPE name IN-GROUP job-attributes-tag COUNT 1
  • EXPECT job-state OF-TYPE unknown|enum IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >2,<10
  • EXPECT job-state-reasons OF-TYPE keyword IN-GROUP job-attributes-tag
  • EXPECT ?job-name OF-TYPE name IN-GROUP job-attributes-tag COUNT 1
  • EXPECT ?job-originating-user-name OF-TYPE name IN-GROUP job-attributes-tag COUNT 1
  • EXPECT ?job-state OF-TYPE unknown|enum IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >2,<10
  • EXPECT ?job-state-reasons OF-TYPE keyword IN-GROUP job-attributes-tag
    EXPECT ?job-state-message OF-TYPE text IN-GROUP job-attributes-tag COUNT 1
    EXPECT ?job-detailed-status-messages OF-TYPE text IN-GROUP job-attributes-tag
    EXPECT ?number-of-documents OF-TYPE integer IN-GROUP job-attributes-tag COUNT 1
    EXPECT ?output-device-assigned OF-TYPE name IN-GROUP job-attributes-tag COUNT 1
  • EXPECT time-at-creation OF-TYPE integer IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >-1
  • EXPECT time-at-processing OF-TYPE no-value|integer IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >-1
  • EXPECT time-at-completed OF-TYPE no-value|integer IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >-1
  • EXPECT job-printer-up-time OF-TYPE no-value|integer IN-GROUP job-attributes-tag COUNT 1
  • EXPECT ?time-at-creation OF-TYPE integer IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >-1
  • EXPECT ?time-at-processing OF-TYPE no-value|integer IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >-1
  • EXPECT ?time-at-completed OF-TYPE no-value|integer IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >-1
  • EXPECT ?job-printer-up-time OF-TYPE no-value|integer IN-GROUP job-attributes-tag COUNT 1
    EXPECT ?date-time-at-creation OF-TYPE no-value|dateTime IN-GROUP job-attributes-tag COUNT 1
    EXPECT ?date-time-at-processing OF-TYPE no-value|dateTime IN-GROUP job-attributes-tag COUNT 1
    EXPECT ?date-time-at-completed OF-TYPE no-value|dateTime IN-GROUP job-attributes-tag COUNT 1
    @@ -489,8 +489,8 @@
    ATTR boolean my-jobs true

STATUS successful-ok

  • EXPECT job-id OF-TYPE integer IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >0
  • EXPECT job-uri OF-TYPE uri IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE "$IPP_URI_SCHEME"
  • EXPECT ?job-id OF-TYPE integer IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >0
  • EXPECT ?job-uri OF-TYPE uri IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE "$IPP_URI_SCHEME"
    EXPECT !job-printer-uri
    EXPECT !job-more-info
    EXPECT !job-name
    @@ -613,8 +613,8 @@
    ATTR keyword which-jobs not-completed

STATUS successful-ok

  • EXPECT job-id OF-TYPE integer IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >0
  • EXPECT job-uri OF-TYPE uri IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE "$IPP_URI_SCHEME"
  • EXPECT ?job-id OF-TYPE integer IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE >0
  • EXPECT ?job-uri OF-TYPE uri IN-GROUP job-attributes-tag COUNT 1 WITH-VALUE "$IPP_URI_SCHEME"
    EXPECT !job-printer-uri
    EXPECT !job-more-info
    EXPECT !job-name

@michaelrsweet michaelrsweet added this to the Stable milestone Mar 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority-low
Projects
None yet
Milestone
Stable
Development

No branches or pull requests
1 participant
@michaelrsweet