We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
How is this outcome possible? We return a failure message on a passing result.
Subject: Failed publicsafety punk replica comparison in production
Failed publicsafety punk replica comparison in production at 2023-06-03 23:09:38.604339
INFO:root: | featurelayer | rowcountdifference | INFO:root: INFO:root: | cscl.AddressPoint | 0.0 | INFO:root: INFO:root: | cscl.Centerline | 0.0 | INFO:root: INFO:root: | cscl.Commonplace | 0.0 | INFO:root: INFO:root: | cscl.Subaddress | 0.0 | INFO:root: INFO:root: replica QA result: pass INFO:root: INFO:root: comparing parent xxx.sde to child yyy.gdb INFO:root: INFO:root: running from zzzzz INFO:root:
The logic starting here looks solid.
geodatabase-replication-toiler/checkreplica.py
Line 28 in 2f2e873
So how does that pass printed in the log exit out to the fail header here?
geodatabase-replication-toiler/geodatabase-scripts/sample-create-punk-replica.bat
Line 38 in 2f2e873
The text was updated successfully, but these errors were encountered:
Saw this behavior again on Sat 8/26/2023 11:14 PM
Sorry, something went wrong.
No branches or pull requests
How is this outcome possible? We return a failure message on a passing result.
Subject: Failed publicsafety punk replica comparison in production
Failed publicsafety punk replica comparison in production at 2023-06-03 23:09:38.604339
The logic starting here looks solid.
geodatabase-replication-toiler/checkreplica.py
Line 28 in 2f2e873
So how does that pass printed in the log exit out to the fail header here?
geodatabase-replication-toiler/geodatabase-scripts/sample-create-punk-replica.bat
Line 38 in 2f2e873
The text was updated successfully, but these errors were encountered: