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.

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

*: Transfer 32-bit test into travis from cirrus #1932

Merged
merged 1 commit into from
Mar 16, 2020

Conversation

chainhelen
Copy link
Contributor

@chainhelen chainhelen commented Mar 14, 2020

  1. 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)

  2. 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

  3. 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
    ...

  4. 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.

  5. 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:

  1. I will close DO_NOT_MERGE DO_NOT_COMMIT DO_NOT REVIEW #1924 once this pr merged or a better way.
  2. travis report display

image

  1. other problem
    There's other question of probability the ci test hang over 10 minutes, need time to find reason .

.travis.yml Outdated
env: go_32_version=1.13
- os: linux
services: docker
env: go_32_version=1.12
Copy link
Contributor Author

@chainhelen chainhelen Mar 14, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cann't use matrix here, for example

env:
   - go_32_version=1.14
   - go_32_version=1.13
   - go_32_version=1.12

when in jobs.include, it have no effect.

.travis.yml Outdated Show resolved Hide resolved
Copy link
Member

@aarzilli aarzilli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@derekparker derekparker merged commit 5774066 into go-delve:master Mar 16, 2020
cgxxv pushed a commit to cgxxv/delve that referenced this pull request Mar 25, 2022
abner-chenc pushed a commit to loongson/delve that referenced this pull request Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants