-
Type:
Build Failure
-
Resolution: Done
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
When testing on MongoDB latest, there is extra log output which breaks the output assertions in the PHPC tests. Here's an example diff:
[2022/10/18 09:34:14.591] FAILURE: (FAILED)
[2022/10/18 09:34:14.591] 001+ {"t":{"$date":"2022-10-18T09:32:38.351Z"},"s":"I", "c":"NETWORK", "id":4648602, "ctx":"main","msg":"Implicit TCP FastOpen in use."}
[2022/10/18 09:34:14.591] Parent executes find with batchSize: 2
[2022/10/18 09:34:14.591] Child executes ping
[2022/10/18 09:34:14.591] OK: Got MongoDB\Driver\Exception\RuntimeException
[2022/10/18 09:34:14.591] --
[2022/10/18 09:34:14.591] Parent waited for child to exit
[2022/10/18 09:34:14.591] Parent executes killCursors
[2022/10/18 09:34:14.591] ===DONE===
[2022/10/18 09:34:14.591] 010+ {"t":{"$date":"2022-10-18T09:32:38.438Z"},"s":"I", "c":"ASIO", "id":6529201, "ctx":"main","msg":"Network interface redundant shutdown","attr":{"state":"Stopped"}}
[2022/10/18 09:34:14.591] 011+ {"t":{"$date":"2022-10-18T09:32:38.438Z"},"s":"I", "c":"ASIO", "id":22582, "ctx":"main","msg":"Killing all outstanding egress activity."}
This occurs in all build variants that test against MongoDB latest.
- is caused by
-
-
- Closed
-