*: Transfer 32-bit test into travis from cirrus #1932
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
32bit docker on cicurs CI
https://github.com/go-delve/delve/runs/501900175
https://github.com/go-delve/delve/runs/501900189
https://github.com/go-delve/delve/runs/498813610
https://github.com/go-delve/delve/runs/498813609
https://github.com/go-delve/delve/runs/498813615
...
This 32bit docker on cirrus CI failed frequency. The erros all have similar memory problems.
Then I do
for ((i=1; i<=300; i++)); do go test -v -test.run TestStepConcurrentDirect ; done
on cirrus CI, see the error every CI period.
(150 loops is enough in fact)
Never reproduct on my local env.
A. 386/centos go1.12.8/go1.13.6/go1.14
B. 386 docker on 64-bit ubunut (kernel 5.3) go1.12.8/go1.13.6/go1.14
amd64 on cicurs CI
Then I try test amd64 on cicurs CI and find same problem as 386.
Also use
for ((i=1; i<=300; i++)); do go test -v -test.run TestStepConcurrentDirect ; done
on cirrus CI, see the same error every CI period.
https://github.com/go-delve/delve/runs/507318116
https://github.com/go-delve/delve/runs/507318112
https://cirrus-ci.com/task/4921825478049792
https://github.com/go-delve/delve/runs/507957824
...
64bit on travis CI
All are ok.
https://travis-ci.com/github/go-delve/delve/jobs/298173516
https://travis-ci.com/github/go-delve/delve/jobs/298173518
https://travis-ci.com/github/go-delve/delve/jobs/298174477
https://travis-ci.com/github/go-delve/delve/jobs/298174479
...
Also
for ((i=1; i<=600; i++)); do go test -v -test.run TestStepConcurrentDirect ; done
on cirrus CI,
I use 600 loops here but all are ok.
32bit on travis CI
https://travis-ci.com/github/go-delve/delve/jobs/298209841
https://travis-ci.com/github/go-delve/delve/jobs/298209842
https://travis-ci.com/github/go-delve/delve/jobs/298209843
...
All are ok, also 600 loops for teststepconcurrent
I think there maybe a problem about 386 docker with specify linux kernel for golang.
(May be similar to golang/go#35777 ?)
Sorry for this crude solution, I can't find a better way about ci failed of cicurs on 386 linux. Platform change is the only thing I can think of. Meanwhile I'm worried about complicating the .travis.yml file
Ps:
There's other question of probability the ci test hang over 10 minutes, need time to find reason .