443d7aad57553f2606be41a934cb4dab46019e09 braney Fri Sep 4 12:10:00 2026 -0700 docent: first eleven regression tests, one per fixed bug, refs #38252 Ten assert the behavior their ticket says is correct; the eleventh is an xfail. All eleven pass against genome-test, 40s for the set. rm35333 bigBed schema vs trackDb type mismatch, no SEGFAULT rm35920 wrong bigBed type in a hub, no crash and no garbage item label rm36029 a MAF displays after several phyloP tracks are on rm36331 quickLift of the GENCODE Archive container, no "Unknown database" rm36514 a chromosome search after a quickLift hop rm36702 quickLift hg19 to hs1, no "Unknown database" rm36798 the two OMIM tracks survive a configure submit rm37388 hgc on a quickLifted hub item, no connect to the source assembly rm37520 lifted tracks survive a hop to another genome and back rm37906 Neandertal tracks draw data in a narrow window on hg18 rm36540 is the xfail, and it is worth reading. The ticket is Closed, but the symptom is present on genome.ucsc.edu (v502), hgwbeta (v503) and genome-test (v503), measured with the reporter's own hub URL as well as with our copy of it: genome= instead of db= for a hub-backed assembly still reaches a query against a chromInfo table that does not exist. There is no fixed behavior to assert, so it is pinned as an xfail and the run fails if it ever starts passing. Six of these build their own state rather than loading the session their ticket names, which is deliberate: a session on someone's account can be renamed or deleted, and hgTracks answers a missing session with a 200 and an early-error page that every noText: assertion passes on. Where a session is genuinely the cheapest way to a state (rm37388), the script also asserts noText: "Could not find session" so that a deleted session fails loudly instead of quietly. Four traps cost a run each and are written into the scripts that hit them, since the next twenty-nine will hit them too: a container never gets an img_data_ row (the rows carry its children's names); a leaf track with no features at the ticket's position has no row either, so a lifted view is better checked by its own quickLiftChain; `track:` sends a plain name and cannot turn on a track in an ATTACHED hub, whose cart variable carries the hub prefix; and asking for one view of a composite turns its sibling views on as well. diff --git src/hg/utils/docent/tests/regress/rm36540.xfail.docent.yaml src/hg/utils/docent/tests/regress/rm36540.xfail.docent.yaml new file mode 100644 index 00000000000..94888a6ecf7 --- /dev/null +++ src/hg/utils/docent/tests/regress/rm36540.xfail.docent.yaml @@ -0,0 +1,32 @@ +# #36540 -- EXPECTED TO FAIL. The ticket is Closed; the symptom is not. +# +# Measured 2026-09-04 with the reporter's own hub URL, not just our copy: +# +# genome.ucsc.edu v502 chromInfo error present +# hgwbeta.soe.ucsc.edu v503 chromInfo error present +# genome-test v503 chromInfo error present +# +# The ticket's last note says "This is now on the RR", and the discussion on it is about +# making the error message better rather than about making genome= resolve. Whatever +# landed, a user who writes genome= instead of db= for a hub-backed assembly still gets +# +# Can't start query: select * from chromInfo where chrom = 'chr9' +# mySQL error 1146: Table 'hs1.chromInfo' doesn't exist (db=hs1) +# +# So this cannot assert fixed behavior, because there is none to assert. It is kept as an +# xfail instead, which is how this suite pins a trap: the run fails if it ever PASSES, so +# the day someone fixes it, they are told there is a test waiting rather than left to +# discover it. If #36540 is reopened and fixed, drop the .xfail from the name. +# +target: genome-test +reset: true +fast: true +db: hs1 +steps: + - goto: "/cgi-bin/hgTracks?genome=hs1&hubUrl=https://hgwdev.gi.ucsc.edu/~braney/docentFixtures/NOTCH2NLHub/hub.txt&position=chr9%3A1-1000000&pix=1100" + + # "chromInfo" alone is the assertion, not the whole quoted string: the message names the + # assembly, and the point is that no query against a chromInfo table should reach the + # user whichever assembly it names. Paired with a row check because the early-error page + # this bug produced draws no image, so noText on its own would have passed on it. + - expect: {rows: [ruler], noText: "chromInfo"}