@fairmint/canton-node-sdk
Version:
Canton Node SDK
137 lines (97 loc) • 7.46 kB
Plain Text
# Patterns of entries to be ignored when checking the canton_network_test log file (sbt checkErrors).
# As the Canton log appenders emit errors/warnings to stdout, the patterns listed here will also be applied when checking the sbt output.
# Patterns must be both
# - PCRE regular expressions (see https://regex101.com) and
# - extended regular expressions as used by "grep -E -e".
# Lines containing only blanks or lines starting with '#' are ignored.
# ExecutionContextMonitor
Task runner .* is .* overloaded
# Reporting aborted test suite
LogReporter - Aborted test suite
# This may sometimes lead to subsequent errors (e.g. api server fails to startup), but quite often it can simply be ignored.
Trying to gather entropy from the underlying operating system to initialized the contract ID seeding, but the entropy pool seems empty.
In CI environments environment consider using the "testing-weak" mode, that may produce insecure contract IDs but does not block on startup.
# We use self-signed ledger API tokens for tests
HMAC256 JWT Validator is NOT recommended for production environments
# Using an access token for a user that has not yet been allocated produces the following warning.
# Users are allocated by the validator app, and all apps are starting concurrently.
PERMISSION_DENIED.*Could not resolve is_deactivated status for user
# Using multiple auth configs for the long-running Canton instances produces the following warning
# when authenticating using an auth config that is not the first in the list.
Could not verify JWT token: The provided Algorithm doesn't match the one defined in the JWT's Header.
# Ignore UNAUTHENTICATED errors logged during the invalid token rejection tests
.*GrpcClientError: UNAUTHENTICATED/.*Request: Tap(13.37)
ErrorBoundary caught an unhandled promise rejection AbortError: The operation was aborted
ErrorBoundary caught an unhandled promise rejection AbortError: Aborted
AbortError: The operation was aborted
TypeError: NetworkError when attempting to fetch resource
oidc login error: NetworkError when attempting to fetch resource
# Testcontainers tries to read the configuration file but it's not available on CI
Attempted to read Testcontainers configuration file at file:
# Output of the oidc-client-ts frontend library. Interaction with Auth0 appears to be unreliable, so
# we ignore all errors and rely on retry loops.
\[oidc-client-ts\]
# Selenium has logged this before, and it has no effect on whether the test passes or not.
NoSuchFileException deleting temporal file.*selenium-manager
# Trying to start a BiDi connection to Firefox repeatedly might fail some attempts with an 405 method not allowed
Invalid Status code=405 text=Method Not Allowed","logger_name":"o.o.s.remote.http.WebSocket"
# TODO(DACH-NY/canton-network-node#7696) revisit after migration of tests to vitest
Trying to re-register template.*
.*GrpcClientError: UNAUTHENTICATED/.*Request: Tap(13.37)
# TODO(#979) Ignore errors related to global domain disconnection and reconnection after sequencers connections changed for now.
# Revisit later to see if we can remove these.
.*NOT_FOUND/UNKNOWN_INFORMEES.*The participant is not connected to any .* where the given informees are known.
.*NOT_FOUND/SUBMISSION_DOMAIN_NOT_READY.*Trying to submit to a disconnected or not configured domain.
# TODO(#975): investigate and remove once fixed
failed with UNKNOWN/channel closed.*SvAppLedgerApiConnectivityIntegrationTest
# This might be logged between the test finishing and shutdown of the nodes (see #8991)
Noticed an DsoRules epoch change.*DecentralizedSynchronizerMigrationIntegrationTest
# TODO (#825): this only applies to simtime.
# In simtime tests where the rounds are advanced too quickly, this trigger might not have enough time to receive the coupon.
# Nevertheless, it is still useful to have the warning in production environments, where this should never happen.
Skipped.*faucet coupons from last claimed round.*to current round
# Sometimes CI the executor seems to take a break, which leads to spurious failed DB activeness checks, see #9388
DB_CONNECTION_LOST.*Database health check failed to establish a valid connection.*Connection is not available, request timed out
# The prometheus export server does not wait for any ongoing requests when shutting down https://github.com/prometheus/client_java/issues/938
The Prometheus metrics HTTPServer caught an Exception while trying to send the metrics response
# TODO (#825): this only applies to simtime.
# Simtime failure, see https://github.com/DACH-NY/canton-network-node/issues/11998#issuecomment-2086304594
INVALID_ARGUMENT.*SequencerTimeoutError
# TODO (#758): find a way to remove this
Encountered 4 consecutive transient failures \(polling interval .*
# TODO (#942): check if we can avoid such errors (they seem to happen when some HTTP API calls race with shutdowns)
unexpected exception: Task slick.*rejected from slick.util.AsyncExecutorWithMetrics
# TODO (#944): investigate what task is it still running and see if we can somehow fix it
Timeout 10 seconds expired, but tasks still running. Shutting down forcibly
ForkJoinIdlenessExecutorService.*shutdown did not complete gracefully in allotted
Consensus not reached.*BftScanConnection:BftScanConnectionTest.*
Consensus not reached.*BftScanConnection:ConfigurationProvidedBftScanConnectionIntegrationTest.*
# internal selenium error. Potentially intermittent
Exception managing firefox: error sending request for url .* http2 error: stream error received: refused stream before processing any application
# TODO(DACH-NY/canton-network-node#18150) - remove this
Vetted state contains multiple entries
# TODO(#645) Remove conversion from future with shutdown to future
Splice unsafe shutdown future
# Scan UI calls round-based endpoints that emit this error, even if we're only interested in the transaction log
.*No data has been made available yet.*
# SV UI polls cometbft status endpoint even when there's no cometBFT (we have this in the full network docker compose test)
.*CometBFT is not configured for this app.*
# Expected during SV onboarding as we start scan and the sv app concurrently
# TODO(#893) maybe remove this again
Failed to read bft sequencers list from scan
Failed to connect to scan of Digital-Asset-Eng-3.*AppUpgradeIntegrationTest
# Ignore scan issues in disaster recovery tests as we don't start scan there
Failed to connect to scan of .*DisasterRecoveryIntegrationTest
Failed to connect to scan of .*AppUpgradeIntegrationTest
Failed to connect to scan of .*ConfigurationProvidedBftScanConnectionIntegrationTest
# Ignore scan connection issues in reonboarding test.
Failed to connect to scan of .*SvDevNetReonboardingIntegrationTest
# Log suppression doesn't seem to work here as the tests use a different logger
GENERIC_CONFIG_ERROR.*SpliceConfigTest
# ExecutorServiceMetrics closes the gauges twice through shutdown and shutownNow in cases where shutdown times out
.*InstrumentDescriptor.*name=daml.executor.* has called close\(\) multiple times
Circuit breaker .* tripped after .* failures.*(Command|Splice)CircuitBreakerTest
# See DACH-NY/cn-test-failures#6328: In rare cases, creating an index asynchronously can fail.
# This is more likely in test code where we run multiple apps against the same database, all trying to create the same index.
Index .* should be created and is invalid, dropping it
# Make sure to have a trailing newline