chore: remove go test cover

[Desiki-high]

Relevant Issue (if applicable)

Details

In golang smoke test, go test don't need coverage analysis and create coverage profile.

Types of changes

What types of changes does your PullRequest introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation Update (if none of the other choices apply)

Checklist

Go over all the following points, and put an x in all the boxes that apply.

• I have updated the documentation accordingly.
• I have added tests to cover my changes.

[codecov]

Codecov Report

Merging #1514 (63e1b24) into master (55a999b) will increase coverage by 0.01%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1514      +/-   ##
==========================================
+ Coverage   62.72%   62.73%   +0.01%     
==========================================
  Files         129      129              
  Lines       44158    44158              
  Branches    44158    44158              
==========================================
+ Hits        27697    27702       +5     
+ Misses      15092    15088       -4     
+ Partials     1369     1368       -1     

see 3 files with indirect coverage changes

[adamqqqplay]

@Desiki-high Does this step affect execution time?

[Desiki-high]

@Desiki-high Does this step affect execution time?

I'm not sure about the execution time. I need to test it.

[Desiki-high]

@Desiki-high Does this step affect execution time?

I'm not sure about the execution time. I need to test it.

In my local machine or Github Action, this step doesn't affect execution time. In my point, the -cover testflag doesn't make any sense.

[adamqqqplay]

@Desiki-high Does this step affect execution time?

I'm not sure about the execution time. I need to test it.

In my local machine or Github Action, this step doesn't affect execution time. In my point, the -cover testflag doesn't make any sense.

@Desiki-high Ok, I see. In addition, if you have time, can you help add the coverage statistics of nydusify and other go modules to codecov? Thanks in advance.

[Desiki-high]

@Desiki-high Does this step affect execution time?

I'm not sure about the execution time. I need to test it.

In my local machine or Github Action, this step doesn't affect execution time. In my point, the -cover testflag doesn't make any sense.

@Desiki-high Ok, I see. In addition, if you have time, can you help add the coverage statistics of nydusify and other go modules to codecov? Thanks in advance.

I can have a try.

[adamqqqplay]

@Desiki-high Does this step affect execution time?

I'm not sure about the execution time. I need to test it.

In my local machine or Github Action, this step doesn't affect execution time. In my point, the -cover testflag doesn't make any sense.

@Desiki-high Ok, I see. In addition, if you have time, can you help add the coverage statistics of nydusify and other go modules to codecov? Thanks in advance.

I can have a try.

Thanks for your help. I will submit an new issue to track this.

[Desiki-high]

@Desiki-high Does this step affect execution time?

I'm not sure about the execution time. I need to test it.

In my local machine or Github Action, this step doesn't affect execution time. In my point, the -cover testflag doesn't make any sense.

@Desiki-high Ok, I see. In addition, if you have time, can you help add the coverage statistics of nydusify and other go modules to codecov? Thanks in advance.

I can have a try.

Thanks for your help. I will submit an new issue to track this.

I have creatd at #1517.