apm-server icon indicating copy to clipboard operation
apm-server copied to clipboard

test: TestAPMServerInstrumentation failing

Open carsonip opened this issue 8 months ago • 0 comments

APM Server version (apm-server version): main

Description of the problem including expected versus actual behavior:

 === RUN   TestAPMServerInstrumentation
    instrumentation_test.go:92: 
        	Error Trace:	/home/runner/work/apm-server/apm-server/systemtest/instrumentation_test.go:92
        	Error:      	Not equal: 
        	            	expected: "102633cf232dd5dfc20f962b726aeb21"
        	            	actual  : "11ae2dc65a581af9577f527e27ea6c87"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-102633cf232dd5dfc20f962b726aeb21
        	            	+11ae2dc65a581af9577f527e27ea6c87
        	Test:       	TestAPMServerInstrumentation
        	Messages:   	expecting log with trace id 102633cf232dd5dfc20f962b726aeb21; got trace id 11ae2dc65a581af9577f527e27ea6c87 and message "request ok" instead
    instrumentation_test.go:94: 
        	Error Trace:	/home/runner/work/apm-server/apm-server/systemtest/instrumentation_test.go:94
        	Error:      	Not equal: 
        	            	expected: "102633cf232dd5df"
        	            	actual  : "11ae2dc65a581af9"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-102633cf232dd5df
        	            	+11ae2dc65a581af9
        	Test:       	TestAPMServerInstrumentation
        	Messages:   	expecting log with transaction id 102633cf232dd5df; got transaction id 11ae2dc65a581af9 and message "request ok" instead
    server.go:145: log file: /home/runner/work/apm-server/apm-server/systemtest/logs/TestAPMServerInstrumentation/apm-server
--- FAIL: TestAPMServerInstrumentation (1.54s)

Steps to reproduce:

Please include a minimal but complete recreation of the problem, including server configuration, agent(s) used, etc. The easier you make it for us to reproduce it, the more likely that somebody will take the time to look at it.

Provide logs (if relevant):

carsonip avatar Jun 19 '25 15:06 carsonip