Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

TestConstantArrivalRateRunCorrectTiming is flaky #1715

Open
na-- opened this issue Nov 9, 2020 · 2 comments
Open

TestConstantArrivalRateRunCorrectTiming is flaky #1715

na-- opened this issue Nov 9, 2020 · 2 comments
Labels
ci tests

Comments

@na--
Copy link
Member

na-- commented Nov 9, 2020

https://github.com/loadimpact/k6/pull/1712/checks?check_run_id=1374326226 produced the following error:

2020-11-09T13:36:16.5863272Z --- FAIL: TestConstantArrivalRateRunCorrectTiming (0.00s)
2020-11-09T13:36:16.5867141Z     --- FAIL: TestConstantArrivalRateRunCorrectTiming/segment_0:1/3_sequence_<nil> (2.00s)
2020-11-09T13:36:16.5870447Z         assertions.go:247: 
2020-11-09T13:36:16.5871148Z                           
2020-11-09T13:36:16.5872620Z 	Error Trace:	constant_arrival_rate_test.go:212
2020-11-09T13:36:16.5873081Z             
2020-11-09T13:36:16.5873330Z 	            	
2020-11-09T13:36:16.5873782Z 			common_test.go:40
2020-11-09T13:36:16.5874031Z             
2020-11-09T13:36:16.5874282Z 	            	
2020-11-09T13:36:16.5874588Z 			minirunner.go:182
2020-11-09T13:36:16.5874895Z             
2020-11-09T13:36:16.5875144Z 	            	
2020-11-09T13:36:16.5875427Z 			helpers.go:86
2020-11-09T13:36:16.5875710Z             
2020-11-09T13:36:16.5875919Z 	            	
2020-11-09T13:36:16.5876249Z 			constant_arrival_rate.go:318
2020-11-09T13:36:16.5876581Z             
2020-11-09T13:36:16.5876832Z 	            	
2020-11-09T13:36:16.5877095Z 			asm_amd64.s:1373
2020-11-09T13:36:16.5877594Z             
2020-11-09T13:36:16.5878349Z 	Error:      	Max difference between 2020-11-09 13:34:49.8011468 +0000 GMT m=+1.108004901 and 2020-11-09 13:34:49.8152531 +0000 GMT m=+1.122092701 allowed is 10ms, but difference was -14.0878ms
2020-11-09T13:36:16.5879066Z             
2020-11-09T13:36:16.5880842Z 	Test:       	TestConstantArrivalRateRunCorrectTiming/segment_0:1/3_sequence_<nil>
2020-11-09T13:36:16.5881647Z             
2020-11-09T13:36:16.5881988Z 	Messages:   	20 expectedTime 1.1s
2020-11-09T13:36:16.5883270Z     --- FAIL: TestConstantArrivalRateRunCorrectTiming/segment_0:1/3_sequence_0,1/3,2/3,1 (2.00s)
2020-11-09T13:36:16.5884787Z         assertions.go:247: 
2020-11-09T13:36:16.5885795Z                           
2020-11-09T13:36:16.5886176Z 	Error Trace:	constant_arrival_rate_test.go:212
2020-11-09T13:36:16.5886547Z             
2020-11-09T13:36:16.5887134Z 	            	
2020-11-09T13:36:16.5887370Z 			common_test.go:40
2020-11-09T13:36:16.5887664Z             
2020-11-09T13:36:16.5888175Z 	            	
2020-11-09T13:36:16.5888482Z 			minirunner.go:182
2020-11-09T13:36:16.5888786Z             
2020-11-09T13:36:16.5889034Z 	            	
2020-11-09T13:36:16.5889751Z 			helpers.go:86
2020-11-09T13:36:16.5890009Z             
2020-11-09T13:36:16.5890257Z 	            	
2020-11-09T13:36:16.5890584Z 			constant_arrival_rate.go:318
2020-11-09T13:36:16.5890916Z             
2020-11-09T13:36:16.5891163Z 	            	
2020-11-09T13:36:16.5891690Z 			asm_amd64.s:1373
2020-11-09T13:36:16.5892122Z             
2020-11-09T13:36:16.5892880Z 	Error:      	Max difference between 2020-11-09 13:34:56.4875962 +0000 GMT m=+7.794368401 and 2020-11-09 13:34:56.4994603 +0000 GMT m=+7.806212601 allowed is 10ms, but difference was -11.8442ms
2020-11-09T13:36:16.5893537Z             
2020-11-09T13:36:16.5894278Z 	Test:       	TestConstantArrivalRateRunCorrectTiming/segment_0:1/3_sequence_0,1/3,2/3,1
2020-11-09T13:36:16.5895006Z             
2020-11-09T13:36:16.5895523Z 	Messages:   	32 expectedTime 1.78s
2020-11-09T13:36:16.5895865Z FAIL
@na-- na-- changed the title TestConstantArrivalRateRunCorrectTiming is flaky on Windows TestConstantArrivalRateRunCorrectTiming is flaky Nov 16, 2020
@na-- na-- changed the title TestConstantArrivalRateRunCorrectTiming is flaky TestConstantArrivalRateRunCorrectTiming is flaky on Windows Nov 16, 2020
@na--
Copy link
Member Author

na-- commented Nov 16, 2020

Another failure: https://github.com/loadimpact/k6/pull/1723/checks?check_run_id=1406188299

--- FAIL: TestConstantArrivalRateRunCorrectTiming (0.00s)
    --- FAIL: TestConstantArrivalRateRunCorrectTiming/segment_1/6:1/2_sequence_1/6,1/2 (2.00s)
        assertions.go:247: 
                          
	Error Trace:	constant_arrival_rate_test.go:212
            
	            	
			common_test.go:40
            
	            	
			minirunner.go:182
            
	            	
			helpers.go:86
            
	            	
			constant_arrival_rate.go:318
            
	            	
			asm_amd64.s:1374
            
	Error:      	Max difference between 2020-11-16 12:11:40.9379141 +0000 GMT m=+9.642533101 and 2020-11-16 12:11:40.9484148 +0000 GMT m=+9.653063201 allowed is 10ms, but difference was -10.5301ms
            
	Test:       	TestConstantArrivalRateRunCorrectTiming/segment_1/6:1/2_sequence_1/6,1/2
            
	Messages:   	29 expectedTime 1.62s
FAIL

@na-- na-- changed the title TestConstantArrivalRateRunCorrectTiming is flaky on Windows TestConstantArrivalRateRunCorrectTiming is flaky Dec 2, 2020
@na--
Copy link
Member Author

na-- commented Dec 2, 2020

It can also fail on linux: https://github.com/loadimpact/k6/runs/1487060610

@na-- na-- mentioned this issue Apr 23, 2021
Closed
@mstoykov mstoykov mentioned this issue May 25, 2021
Merged
@na-- na-- mentioned this issue Aug 16, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ci tests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@na--